-
Notifications
You must be signed in to change notification settings - Fork 67
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
Vector query with "where" clause returns incorrect count #5468
Labels
bug
Something isn't working
Comments
mattnibs
added a commit
that referenced
this issue
Nov 25, 2024
Fix issue with incorrect counts when using where clauses on a aggregation function in vector runtime. If a value fails the where clause make the value as null so it is skipped by the aggregation function. Closes #5468
mattnibs
added a commit
that referenced
this issue
Nov 25, 2024
Fix issue with incorrect counts when using where clauses on a aggregation function in vector runtime. If a value fails the where clause make the value as null so it is skipped by the aggregation function. Closes #5468
mattnibs
added a commit
that referenced
this issue
Nov 26, 2024
Fix issue with incorrect counts when using where clauses on a aggregation function in vector runtime. If a value fails the where clause make the value as null so it is skipped by the aggregation function. Closes #5468
mattnibs
added a commit
that referenced
this issue
Nov 26, 2024
Fix issue with incorrect counts when using where clauses on a aggregation function in vector runtime. If a value fails the where clause make the value as null so it is skipped by the aggregation function. Closes #5468
Verified in super commit f030936. The query now returns the correct count.
Thanks @mattnibs! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Repro is with super commit 411514f.
This is a simplification of the bench2/q4 query.
Test data is the contents of repro.jsup.gz:
This query against the original Super JSON returns the expected result.
However if I turn the Super JSON into Super Columnar and repeat the same query, now the counts are too high.
If I drop the
where
clause, the results match.The text was updated successfully, but these errors were encountered: