Repository navigation
[core] Share MERGE action evaluation for distributed execution - #1203
Merged
Merged
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
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.
Summary
MergeBatchExecutionfor Arrow batches that have already been joined by an execution engine. Rust compiles SQL conditions once and owns action selection, assignment casting, target passthrough and typed insert nulls.The action order and target passthrough follow the current Spark
MergeIntoPaimonDataEvolutionTableimplementation. The new evaluator has no Ray or table I/O dependency; callers still own joins, planning and authorization. No dependencies are added.Verification
Companion Python PR apache/paimon#10761 remains draft until this API is on Rust main; Python Native CI continues to build main.