Inital changes to support PointValues with Summary information for timeseries use case #1
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.
Description
Support faster range queries on
timestamp
field by using precomputed (while indexing) aggregated stats (such asmin, max, count, sum, avg
or any other decomposable aggregation function) onmeasurement
associated with atimeseries
point.Changes
Usage
Index
Search
Stats merge function definiton
Sum
Long max fn
Comparison with DocValues
Below is the comparison of running unit test for DocValue approach vs TSPoint approach -
This test ingests
10000000
docs against a given TSID and performs a range query on timestamp 100 times against the same TSID. Merge function used issum
.This is not apple to apple comparison since number of segments are 3 in DocValues approach whereas its 10 in TSPoint approach.
Limitation of this feature
timestamp
.TODOs
TSPoint
. Currently its hardcoded inFieldInfo.java
which isn't the right place to define them.New interfaces
Compression of values and timestamp