GH-38750: [Python] Adding 3 operators to DNF filter expression #38774
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
|
|
JacekPliszka
changed the title
…pache#38774) Adding is_nan, is_null and is_valid operators to DNF filter expression.
JacekPliszka
changed the title
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.
Rationale for this change
The old expression DNF format of filter expressions is convenient for some uses but is missing null handling.
This PR adds null/not-null handling to the format.
#34504
#38750
What changes are included in this PR?
Only the filter_expression operators are added.
Are these changes tested?
I would like to first get some prelimiary approval as this function is marked with DeprecationWarning
Are there any user-facing changes?