Repository navigation
feat(go): expose catalog database and table creation - #1462
Merged
Merged
Conversation
JingsongLi
approved these changes
Nov 20, 2026
This was referenced Nov 20, 2026
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
Closes #1461
Allow Go applications to create databases and tables through the existing catalog.
Brief change log
Catalog.CreateDatabaseandCatalog.CreateTable.Tests
cargo +1.95.0 test --locked -p paimon-c(103 passed).CGO_ENABLED=1 go test -count=1 ./...andCGO_ENABLED=1 go vet ./...inbindings/go/tests, using the rebuilt macOS arm64 library.API and Format
Adds two Go methods and two C exports. The storage format is unchanged.
Documentation
Adds a Go provisioning example.<!--
Thank you very much for contributing to Paimon Rust - we are happy that you want to help us improve it. To help the community review your contribution in the best possible way, please go through the checklist below, which will get the contribution into a shape in which it can be best reviewed.
Contribution Checklist
Make sure that the pull request corresponds to a GitHub issue. Exceptions are made for typos in documentation or comments, which need no issue.
Fill out the template below to describe the changes contributed by the pull request. That will give reviewers the context they need to do the review.
Make sure that the change passes the automated tests, i.e.,
cargo testpasses.Each pull request should address only one issue, not mix up code from multiple issues.
(The sections below can be removed for hotfixes or typos)
-->
Purpose
Linked issue: close #xxx
Brief change log
Tests
API and Format
Documentation