JingsongLi opened a new pull request, #10761:
URL: https://github.com/apache/paimon/pull/10761

   ## Summary
   
   - Dispatch Ray MERGE condition/action batches through the selected execution 
backend instead of unconditionally importing the Python executor.
   - Connect update, delete, insert and self-MERGE workers to the new Rust Core 
action evaluator through a thin Native adapter.
   - Share the existing Native MERGE clause/callback transport, preserve 
coalesced ON aliases and explicit callable read projections, and compile worker 
operators lazily with serialization-safe state.
   - Preserve the optional runtime selection boundary: an absent SDK can select 
Python before execution; a missing API in an installed SDK or any execution 
error is propagated.
   
   Public Python APIs, Ray joins, snapshot capture, authorization and 
write/commit boundaries retain their existing responsibilities. Native 
execution does not import the Python backend. No dependencies are added.
   
   ## Verification
   
   - 20 protocol/backend-isolation tests passed.
   - 13 focused real Ray tests passed, covering ordered clauses, NULL 
fallthrough, renamed ON keys, update/delete interaction, inserts and self-MERGE 
callable behavior.
   - 38 existing local MERGE/execution-boundary tests passed.
   - Arrow 16 compatibility run: 25 passed, 4 skipped (unavailable optional 
extras).
   - All 4 new real Native adapter cases passed against the actual SDK 
class/Core in the companion Rust PyO3 test executable. No local Native 
extension was installed or rebuilt.
   - Flake8 and diff checks passed.
   
   ## Dependency
   
   Depends on apache/paimon-rust#1203. Native CI continues to build Rust main, 
so this PR remains draft until the new Core/binding API is merged. No version 
probes or compatibility fallback are added.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to