Elastic Avg: engine queries Rate but planner precomputes Sum+Count #456

Activity

1. milindsrivastava1997

   added

   bugSomething isn't workingSomething isn't working

   asap-query-engine

   on Jun 27, 2026
2. milindsrivastava1997 commented on Jun 28, 2026

   

   milindsrivastava1997

   on Jun 28, 2026

   ContributorAuthor

   More actions

   Fixed in this branch by returning None from build_query_metadata_elastic for Avg queries (elastic.rs), which causes graceful fallback to Prometheus — the same behavior SQL and PromQL already have for Avg (SQL's parse_single_statistic returns None when the statistic maps to multiple values; PromQL's context builder returns None when statistics_to_compute.len() != 1).

   The previous code used Statistic::Rate for Avg, which was completely wrong — the planner precomputes [Sum, Count] (two separate MultipleSum accumulators), not a rate accumulator. This would have returned incorrect results rather than falling back.

   Properly serving Avg requires querying both the Sum and Count accumulators then dividing — that's a deeper engine change tracked in a follow-up issue.
3. milindsrivastava1997

   linked a pull request that will close this issuefix(query-engine): update Elastic path to return None for avg instead of mistakenly returning rate #464on Jun 28, 2026
4. milindsrivastava1997

   closed this as completedin #464on Jun 28, 2026