49d1be30e7
It's a bit of a duck-type hack, but if we wanna just `ParquetFileChunk` in the new architecture, we somehow need it to accept new-gen paths. Also path handling should be somewhat centralized since ingester/compactor/querier all need to construct them. So having a `ParquetFilePath` that supports both path styles seems to be a not-to-bad solution. This should obviously be cleaned up in some not-to-distant future. |
||
|---|---|---|
| .. | ||
| src | ||
| Cargo.toml | ||