JingsongLi opened a new pull request, #10622: URL: https://github.com/apache/paimon/pull/10622
## Purpose Use Rust to execute the REST version-management operations that PyPaimon already exposes: tag create/get/delete, paginated tag listing, latest-snapshot loading and guarded snapshot/tag rollback. ## Changes - Extend the existing Native REST branch adapter into a catalog adapter and delegate these operations to Rust core. - Keep PyPaimon's public response and exception types, table UUID and expected-head guards, authentication configuration and credential refresh behavior. - Only select a backend before execution. A failed Native request is never replayed through Python, and this bridge performs no local publication cleanup. - Match Java's optional rollback fields and pagination semantics, including empty continuation tokens, whitespace prefixes and null versus empty tag pages. - Handle JSON `null` responses as absent values when deserializing REST metadata. - Extend CI's Native bridge verification while continuing to build paimon-rust from `main`. - Add real HTTP tests covering Native-only execution, V4 request signing, Unicode branch/tag paths, snapshot metadata preservation, 403/404/409/501 errors, absent Native operations, empty tables, and rejected UUID/head guards. ## Dependency This PR requires https://github.com/apache/paimon-rust/pull/1142 to be merged first. CI continues to consume Rust `main`; it is not pinned to a feature branch. ## Verification - PyPaimon Native version/branch/read-write regressions with all four Native flags enabled. - Existing REST protocol, API, tag, branch and read/write regressions — 160 tests and 11 subtests passed. - Dedicated Native version-management and shared-data branch lifecycle tests, including the additional review regressions — 73 tests passed. - Flake8 and `git diff --check`. -- 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]
