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

   ### Purpose
   
   Use Native planning/reading and Native MERGE sources for PyPaimon's existing 
batch `scan.mode=latest`, `latest-full`, and `from-snapshot-full` routes, 
following current Java semantics.
   
   Depends on https://github.com/apache/paimon-rust/pull/1155. Keep this draft 
until the Rust change is merged. Native CI continues to build Rust `main`; no 
fallback or CI override is added to conceal the dependency.
   
   ### Changes
   
   - Allow those already supported source modes through the Native MERGE 
qualifier. Existing scan-option validation, source schema, authorization 
eligibility and snapshot handling remain in place.
   - Add 148 REST integration cases across append/PK/Data Evolution tables: 
Arrow, batch reader and row iterator reads, hidden predicate fields with LIMIT, 
complete historical/latest snapshots, empty tables, and batch/stream MERGE 
commits. Native cases reject Python fallback and source materialization.
   - Document the existing batch mode semantics. Production Python changes are 
limited to the Native source-mode qualifier.
   
   ### Validation
   
   - Existing Python paths for the new cases: **74 passed**.
   - Existing Native MERGE suite: **60 passed**.
   - The old installed Rust extension reproduces the Native `latest` rejection, 
which is fixed by the dependency above. The other 74 Native cases must run 
against the updated Rust `main` in CI after that PR merges.
   - Flake8 for changed Python files and `git diff --check`: passed.
   - The installed extension was not rebuilt or installed during validation.
   - Independent Python/source/authorization/test review completed without a 
remaining concrete finding.
   


-- 
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