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

   ## Summary
   
   Depends on https://github.com/apache/paimon-rust/pull/1086. Keep this draft 
until that change reaches Rust main; the Native CI job continues to build 
upstream main.
   
   PyPaimon already supports source-backed primary-key BTREE/BITMAP indexes. 
Native planning currently returns data splits and then performs index-manifest 
loading, evaluation and split refinement in Python. The companion Rust change 
owns those operations in core.
   
   - Use the Native planner's refined splits directly and remove the redundant 
Python sorted-index pass.
   - Remove PK sorted-index-specific LIMIT deferral; Rust owns PK distribution 
and refinement, and the reader still applies residual predicates and LIMIT.
   - Keep the existing mocked sorted-index test on the classic Python lane. Add 
real REST Native tests using Java-generated BTREE/BITMAP data and index files.
   
   The REST tests cover source-backed and uncovered files, 
conjunction/disjunction with residual predicates, historical snapshots, 
unavailable index files, nonzero row IDs, index disablement, limits/shards and 
a newer PK version whose value no longer matches the old index.
   
   ## Validation
   
   - 1033 tests and 5 subtests passed across twelve related suites with all 
five Native switches enabled, using the companion Rust build.
   - Native counters: plan 1347, read 1454, write 720, commit 336. All update 
families exercised: row_id 90, grouped 54, predicate 63, upsert 38, incremental 
116, merge 33.
   - The new REST suite has 15 cases; both core/integration review and an 
independent test audit completed.
   - Flake8 and Python 3.6 syntax checks passed for changed files.
   
   No Rust fork/ref override or compatibility fallback is introduced.
   


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