JingsongLi opened a new pull request, #10471: URL: https://github.com/apache/paimon/pull/10471
### Purpose Verify the existing PyPaimon REST BLOB view capability through Native reads and MERGE table sources, using Java's dependency context and upstream FileIO semantics. Depends on https://github.com/apache/paimon-rust/pull/1085. This PR is draft until that core fix is merged. Native CI continues to build paimon-rust `main`; no fork/ref pin or compatibility fallback is added. The original native extension fails with 403 when the REST service requires `X-Paimon-Read-Via`, while the classic Python reader succeeds. These tests keep the existing Python capability and require the native implementation to produce the same result. - Direct/nested view reads retain the outermost table identity, NULL values, and descriptor output. - Native MERGE consumes a view table source without Python materialization. - A signed S3 fixture rejects the wrong table's data token and forces upstream token refresh without sleeps. - Multiple BLOB fields share one upstream metadata/snapshot scan; field IDs remain correct after dropping an ordinary column. - Branch identifiers, explicitly supplied outer Read-Via, and denied dependencies retain their semantics. - Native cases reject reader/source fallback rather than silently passing through Python. ### Tests Built the local extension with the Rust core fix and ran nine suites with `PYPAIMON_TEST_NATIVE_PLAN`, `READ`, `WRITE`, `UPDATE`, and `COMMIT` all enabled: **983 passed**. Counters confirmed native plans (1268), reads (1387), writes (686), commits (336), and every update family. The final Blob-view selection was also independently verified: **19 passed**. Flake8, Python 3.6 syntax parsing, and `git diff --check` passed. -- 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]
