-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Add support for Bloom filters on unsigned integer columns in Parquet tables #9770
Conversation
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.
Thank you very much @progval 🙏
Can we please add tests for this code (so that we don't accidentally break it in some future refactoring?)
Hi @progval -- do you think you will have time to add some tests briefly I noticed that #9778 only adds tests for the signed ( |
yes that's what I had in mind |
Ok, #9778 has now been merged. Sorry for the delay |
Tests added. There is some code in common with #9888 (to build the test data) but they shouldn't merge-conflict |
They did, but I just fixed it. |
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.
@@ -452,6 +452,144 @@ int_tests!(16, correct_bloom_filters: false); | |||
int_tests!(32, correct_bloom_filters: true); | |||
int_tests!(64, correct_bloom_filters: true); | |||
|
|||
// $bits: number of bits of the integer to test (8, 16, 32, 64) |
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.
I didn't realize UInt8
and UInt16
were also affected. 💯 for testing
Which issue does this PR close?
Closes #9769.
Rationale for this change
What changes are included in this PR?
Also fixed
prune_int $bits _scalar_fun_and_eq
(on signed integers) to run the query it should have been running.Are these changes tested?
They are not, but the code is straightforward so I don't think tests would be useful.
Are there any user-facing changes?
It should be invisible other than a performance improvement.