16bd3e67c0
Instead of using some hand-rolled timestamp-based logic (or just "unknown") all over the place, just use logic introduced in #5017. This requires slightly improved table summaries within the querier that at least has min/max for the timestamp column. For that, the former `IngesterChunk`-specific `calculate_summary` method was extended to `create_basic_summary` to include that data and is now also used by `QuerierParquetChunk`. Note: `QuerierRBChunk` already has detailled metrics that are provided by the read buffer implementation. Should we ever need even better pruning for `QuerierParquetChunk` (or `IngesterChunk`) then we _only_ need add extra data to the table summaries. Closes #4976. Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| data | ||
| server | ||
| stream_handler | ||
| compact.rs | ||
| data.rs | ||
| handler.rs | ||
| job.rs | ||
| lib.rs | ||
| lifecycle.rs | ||
| poison.rs | ||
| querier_handler.rs | ||
| query.rs | ||
| server.rs | ||
| test_util.rs | ||