feat(metricsql): parse l2_over_time - #9
Merged
Conversation
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
1 participant
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.
MetricsQL evaluation includes
l2_over_time(range-vector), but the shared ProjectASAP parser currently rejects it before Planner lowering can select a UnivMon summary.This adds the MetricsQL function signature as a matrix-to-vector range reducer and covers its parsed AST alongside the existing
distinct_over_timeandentropy_over_timeextensions.Before this PR,
l2_over_time(metric[5m])failed at the parser boundary. After this PR, it reaches the Planner frontend, where the separate UnivMon execution work can lower and bind it.Verification:
cargo +1.98.0 fmt -- --checkcargo +1.98.0 test parser::parse::tests --lib(14 passed)This PR only defines syntax and type shape. It does not claim Planner lowering or runtime execution support.