Repository navigation
[python] Keep REST catalog operations on Python - #10622
Merged
JingsongLi merged 2 commits intoOct 17, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
Keep PyPaimon's REST catalog operations on the Python HTTP client. These metadata calls do not benefit from a Native bridge, while Native table planning, reading, writing and committing continue to execute in Rust.
Changes
RESTApidirectly for all branch, tag, snapshot-loading and rollback entry points.pypaimon_rustduring metadata calls, even when Native table options are enabled.Rust's public REST catalog APIs remain in the independent paimon-rust PR.
Verification
git diff --checkpassed.