We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
System info: [1.2.0, CentOS 7]
Steps to reproduce:
test value=1 1488252141000000000 test value=2 1488252151000000000 test value=3 1488252161000000000
SELECT max("value")*1000,min("value")*1000 from test where time>1488252131s
Expected behavior:
time max min ---- --- --- 1488252131000000000 3000 1000
Actual behavior:
time max min ---- --- --- 1488252141000000000 1000 1488252161000000000 3000
Additional info:
if delete the multiply operator,the result is what I expected
SELECT max("value"),min("value") from test where time>1488252131s time max min ---- --- --- 1488252131000000000 3 1
and in old version(v0.11.0),the result is always return 1 line with start query time.
The text was updated successfully, but these errors were encountered:
It looks like it somehow got tricked into thinking that you had two selectors and didn't normalize the time for each one. I'll take a look at it.
Sorry, something went wrong.
Closing this in favor of #8167.
No branches or pull requests
Bug report
System info: [1.2.0, CentOS 7]
Steps to reproduce:
Expected behavior:
Actual behavior:
Additional info:
if delete the multiply operator,the result is what I expected
and in old version(v0.11.0),the result is always return 1 line with start query time.
The text was updated successfully, but these errors were encountered: