fix(query-engine): normalize topk labels in binary expressions - #644
Merged
Conversation
milindsrivastava1997
marked this pull request as ready for review
August 27, 2026 17:40
milindsrivastava1997
marked this pull request as draft
August 27, 2026 17:40
milindsrivastava1997
marked this pull request as ready for review
August 27, 2026 19:53
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #631. PromQL
topk(...)binary arms now use the original non-__name__labels for intermediate vector matching. Standalone Topk output formatting remains unchanged.The fix covers instant and range paths, including
topk + plain,topk + topk, scalar arithmetic, empty joins, and all supported arithmetic operators.Validation
query_engine_rusttest suitecargo fmtcargo checkcargo clippyAll checks pass.