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
Currently presto aggregate function max seems to ignore NaN . As can be seen from the queries below.
c++ ====================================== presto:feed> select max(x) from (values 4.0,nan(),null) T(x); 4.0 presto:feed> select max(x) from (values nan(),nan(),null) T(x); -1.7976931348623157E308 presto:feed> select min(x) from (values 4.0,nan(),null) T(x); NaN presto:feed> select min(x) from (values nan(),nan(),null) T(x); NaN java ===================================== presto:feed> select max(x) from (values 4.0,nan(),null) T(x); 4.0 presto:feed> select max(x) from (values nan(),nan(),null) T(x); NaN presto:feed> select min(x) from (values 4.0,nan(),null) T(x); 4.0 presto:feed> select min(x) from (values nan(),nan(),null) T(x); NaN
N/A
No response
The text was updated successfully, but these errors were encountered:
Notice that in Java, for some reason, the order matters:
presto:di> select max(x) from (values 4.0,nan(),null) T(x);; _col0 ------- 4.0 (1 row) presto:di> select max(x) from (values nan(),4.0,null) T(x); _col0 ------- NaN (1 row)
This might be a bug in Java. Worth creating an issue in prestodb to ask.
Sorry, something went wrong.
Created issue here : prestodb/presto#21877 .
kgpai
Successfully merging a pull request may close this issue.
Bug description
Currently presto aggregate function max seems to ignore NaN . As can be seen from the queries below.
System information
N/A
Relevant logs
No response
The text was updated successfully, but these errors were encountered: