Flink: Support CREATE VIEW, DROP VIEW and ALTER VIEW RENAME in FlinkCatalog - #17873
Open
talatuyarer wants to merge 2 commits into
Open
Flink: Support CREATE VIEW, DROP VIEW and ALTER VIEW RENAME in FlinkCatalog#17873talatuyarer wants to merge 2 commits into
talatuyarer wants to merge 2 commits into
Conversation
…s, along with related test cases for view operations.
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.
Adds the write path for Iceberg views to the
Flink v2.3, following the read path in #17859 (part of #17858):Following commands are implemented:
CREATE VIEW [IF NOT EXISTS]with comment and column listDROP VIEW [IF EXISTS]ALTER VIEW ... RENAME TOALTER VIEW ... ASnow fails with a clear "Altering a view is not supported yet" instead of a misleading internal error; implementation is the next PR in the series.CREATE OR REPLACE VIEWis intentionally absent. Flink (through 2.3) has no dispatch path for it on catalog views, so nothing ever reaches the catalog.