[#6578] docs(catalog): Add Fluss catalog support design#10896
Open
xxubai wants to merge 2 commits intoapache:mainfrom
Open
[#6578] docs(catalog): Add Fluss catalog support design#10896xxubai wants to merge 2 commits intoapache:mainfrom
xxubai wants to merge 2 commits intoapache:mainfrom
Conversation
Code Coverage Report
|
Author
|
Can you take a look for this design? @roryqi @jerryshao |
Contributor
|
Sure, I will. Sorry for late response. |
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.
What changes were proposed in this pull request?
This PR adds a design document for Apache Fluss catalog support in Gravitino.
The document covers:
catalog-flussmodule and catalog properties such asbootstrap.servers.Why are the changes needed?
Issue #6578 proposes supporting Apache Fluss catalog integration in Gravitino. Fluss is a streaming storage system for real-time analytics, and native catalog support would allow Fluss metadata to be managed through Gravitino's unified catalog, schema, table, partition, and governance APIs.
Fix: #6578
Does this PR introduce any user-facing change?
No. This PR only adds a design document.
The document proposes future user-facing concepts such as
provider=fluss,bootstrap.servers, and Flink/Spark bypass property conventions, but does not implement them in this patch.How was this patch tested?
Not run. This is a documentation-only design proposal.