New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LATEST considers a bucket whose start time doesn't fall within [fromTimestamp, toTimestamp] #1486
Comments
This seems like a bug. We will try to reproduce it. Regarding
Note that when aggregating over a compacted time series, the timestamps represent the start timestamp of the raw buckets. |
…ater then the lastest sample it shouldn't be includede in the result
…ater then the lastest sample it shouldn't be includede in the result
…ater then the lastest sample it shouldn't be includede in the result
…ater then the lastest sample it shouldn't be includede in the result (cherry picked from commit 16f7103)
…ater then the lastest sample it shouldn't be includede in the result (cherry picked from commit 16f7103)
…ater then the lastest sample it shouldn't be includede in the result (cherry picked from commit 16f7103)
…ater then the lastest sample it shouldn't be includede in the result (cherry picked from commit 16f7103)
Fixed in RedisTimeSeries 1.8.11 |
Hi, having an issue with
LATEST
. Having an hourly compaction series with the following data:Making the following query includes the latest compacted value whose start time doesn't fall within
[fromTimestamp, toTimestamp]
.From: Jun 01 2023
To: Jun 30 2023
Returned: Jan 17 2023
What's wrong?
On a side note I'd also like a clarification on what
ALIGN
does:Would this query correctly aggregate ONLY values of timestamps between fromTimestamp to toTimestamp into a single bucket considering ALL points which fall in between from and to? The documentation on ALIGN is a bit ambiguous to me.
As I understand, without ALIGN keyword, there could be multiple buckets, not really falling in between from and to, so I would like to clarify that ALIGN serves my use case.
Thanks!
The text was updated successfully, but these errors were encountered: