You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Range queries drop self-keyed accumulator expansion (top-k) for single-population metrics #584
execute_range_query_pipeline's single-population branch (no separate keys_query) uses each value group's own group_key directly and never calls get_keys() on the value accumulator itself. The instant path (collect_results_same_aggregation) does call it, which is how self-keyed accumulators like CountMinSketchWithHeap (top-k) expand into multiple output keys without a separate keys aggregation. A range query over such a metric, grouped by None at the store level, returns empty instead of the expanded top-k keys.
This predates #580/#582 — the original code also unconditionally skipped None-keyed groups in this branch — so it's a distinct, pre-existing gap, not a regression from that fix.
Activity
fix(query-engine): don't let self-keyed value accumulators override k…
Merge origin/main (#587) into #583: reconcile per-step keys with self…
test(query-engine): add differential PromQL testing infra (#590, #594) (