[rest] Add database branch and tag APIs - #9879
Draft
JingsongLi wants to merge 4 commits into
Draft
JingsongLi wants to merge 4 commits into
JingsongLi wants to merge 4 commits into
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
Add database-level writable branches and immutable tags to the REST client and protocol, exposed through
RESTCatalog.treeManagement(). Callers can page through references, inspect a reference, create a branch or tag from an existing reference, fast-forward a branch to an immutable tag, and delete references.TreeManagementandRESTTreeManagement, reusing the catalog's configured HTTP client, authentication, and prefix./treesendpoints, reference models,DatabaseReferenceResponse, pagination, and HTTP client support to the REST OpenAPI specification and client.POST /v1/{prefix}/databases/{database}/trees/{name}/forward, following the table-level forward operation's path and HTTP method.This PR provides the reference-management client and protocol surface. Reference persistence requires a catalog server implementation.
Tests
mvn -pl paimon-core -am -DwildcardSuites=none -DfailIfNoTests=false -Dtest=RESTCatalogTreeManagementTest,RESTApiDatabaseReferenceTest test— 7 tests covering catalog configuration, branch/tag operations, the forward route and JSON body, pagination, and error propagation; Checkstyle, Spotless, and Enforcer enabled.git diff --check.