-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
query/api: properly pass downsampling param #1144
Conversation
As compact.ResolutionLevel{Raw,5m,1h} says the resolution levels are expressed in milliseconds. Currently, parseDownsamplingParam() calls parseDuration() and friends which express this value in nanoseconds. Thus, we need to divide the value by 1000*1000 to have them in milliseconds. Add test cases to check all of this.
this lgtm, but we should note this change in the changelog |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add changelog, nice job on tests! 🎖️
Wow 😱 |
I think we should close like at least 3 tickets mentioning that choosing downsampling does not always work ;p |
This is wrong change IMO - the time is being divided to match miliseconds further down in stack ): And we are trying to somehow adjust unit in vatiable with unit agnostic type - time.Duration ): Hopefully we are on it here: #1146 Consequence is that downsampling is technically never working now. Should we revert this maybe? Unless I am wrong @GiedriusS (: |
This reverts commit 7a767ef. # Conflicts: # CHANGELOG.md
As compact.ResolutionLevel{Raw,5m,1h} says the resolution levels are
expressed in milliseconds. Currently, parseDownsamplingParam() calls
parseDuration() and friends which express this value in nanoseconds.
Thus, we need to divide the value by 1000*1000 to have them in
milliseconds.
Add test cases to check all of this.