[Parquet] Arrow Coercion & SBBF Check Functions #5661
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Closes #5550.
Rationale for this change
I posted a long-winded explanation on the issue.
What changes are included in this PR?
arrow::coerce_to_parquet_typepublic function. This allows crate users to use the same coercion logic that occurs in Arrow writer.arrow::sbbf_check, that evaluates an Arrow array against a bloom filter after coercing the values to a target Parquet type. This returns aBooleanArray.Are there any user-facing changes?
There are two additional public functions (mentioned above). I will add more tests and documentation. There is also some necessary cleanup work (obvious in some areas). Opening this draft to get feedback on the overall direction before proceeding.