Added support for multiple aggregators for TS range commands#1670
Merged
Conversation
|
coverage: 92.847% (+0.01%) from 92.837% — vv-ts-multiple-aggregators into main |
tillkruss
approved these changes
Apr 22, 2026
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
3 participants
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.
Currently, the AGGREGATION clause in Time Series range commands supports only a single aggregator per command. Retrieving multiple aggregations (e.g., both min and max for candlestick charts) requires multiple consecutive calls, resulting in:
Performance degradation (~Nx slower for N aggregators)
Potential data inconsistency if data is added, deleted, or expired between calls
This feature allows users to specify multiple aggregators in a single command, improving both performance and data consistency.