chore: Move remaining expressions to spark-expr crate + some minor refactoring #1165
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 #659
Rationale for this change
This PR moves the final expressions (
NegativeExpr,UnboundColumn, andCheckOverflow) to the spark-expr crate.The only expressions remaining in
coreare the bloom filter expressions, which depend on the parquet package, and subquery, which depends on JNI. I think we can leave these ones in core.What changes are included in this PR?
NegativeExpr,UnboundColumn, andCheckOverflowfromcoretospark-exprdatafusionsubpackage, so thatoperatorsandexpressionare directly underexecution(we previously had twooperatorspackages)shuffle_writertoexecution::shufflepackageCometExpandExectoExpandExecfor consistency with other exec namingHow are these changes tested?