JingsongLi opened a new pull request, #10781: URL: https://github.com/apache/paimon/pull/10781
## Purpose Remove dispatch bridges that always entered the Python executor. These helpers have no Native execution callers; Rust handles the corresponding work internally through its writers, MERGE execution, path selection and authorization readers. ## Changes - Move the per-row key extractor factory into its Python execution module, preserving bucket modes and error behavior. - Let existing public per-row, Ray MERGE condition, external path and authorization callback helpers lazily delegate directly to their Python implementations. - Delete four fixed-Python wrappers from write backend dispatch and the fixed row-filter wrapper from read dispatch. - Preserve public signatures, the overridable row-key and authorization callback methods, authorization rule order, and empty-rule/path guards. Shared validation remains outside execution. ## Verification - Public helper, external path, authorization, deferred Blob and shared import tests: 135 passed. - Python writer, sequence field and aggregation tests: 170 passed. - Joint SDK/PyPaimon import-boundary, routing, authorization and structured read tests: 262 passed; 12 Native plans and 48 Native reads exercised. Four Daft grouped-write cases were outside this targeted run. - The joint suite includes a fresh SDK-process temporal read that rejects Python execution imports. It uses an existing Cargo test executable, without rebuilding or installing an extension into Python environments. - Repository Flake8 for all changed files and git diff whitespace checks passed. - Independent caller and diff review found no Native callers, stale dispatch references, import cycles or remaining actionable findings. No Rust changes or new SDK interfaces are needed. -- 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]
