Repository navigation
Conversation
Proposes mirroring StarRocks Materialized View registrations into the configured Iceberg catalog (HMS/Iceberg REST Catalog) so MVs are discoverable by external systems, while StarRocks continues to own and serve them natively. Companion to StarRocks/starrocks#78193.
|
Tick the box to add this pull request to the merge queue (same as
|
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.
Summary
Adds a design doc under
sigs/Data Lake Analytics/proposing to mirror StarRocks Materialized View (MV) registrations into the configured Iceberg catalog (HMS or Iceberg REST Catalog), so MVs are discoverable by external systems (data registries, governance tools, other query engines) while StarRocks continues to own and serve them natively.Companion feature-request issue with problem statement / goals / phasing: StarRocks/starrocks#78193
Highlights
default_catalogauthz bypass) → Phase 2a/2b (full spec compliance + cross-engine data interoperability) → Phase 3 (native dual-write, long-term).Posting here per the SIG-owned design doc convention (see
sigs/Data Lake Analytics/[StarRocks] New DLA FrameWork.pdf), for review/discussion ahead of implementation.