Add RunEndEncoded type coercion #18561
Merged
+171
−1
Conversation
This file contains hidden or 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
Weijun-H
approved these changes
Nov 11, 2025
Member
|
Thanks @alamb for reviewing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 #18516, although it does still not allow for doing
SELECT * WHERE ree_encoded_column_name = 'test'because we don't have the necessary cast support available yet. See the issue for more details.What changes are included in this PR?
Type coercion logic for RunEndEncoded types to datafusion-expr-common. I've basically tried to copy what's done for dictionaries. It's quite possible I missed something!
Are these changes tested?
Yes, adds new tests for type coercion of REE types to datafusion-expr-common.