chore: add aliases for group window based on cardinality on use case #202
Conversation
This file contains 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.
Related to influxdata/influxdb#22350
This provides aliases that can be used to generate queries for group-window queries based on a use-case, rather than the use case of
group-window-transposewith different types yielding the high or low cardinality versions of the queries.The reasoning for this may seem opaque currently, but this should help make the logic for influxdata/influxdb#22480 much simpler, and allow for the high and low cardinality versions of the queries to be created for the correct time range.
The existing use-case is not being removed at this time, so this is purely an additive change and will not break any existing behaviors.