[core][spark] Support history-preserving replace table#7860
Open
Zouxxyy wants to merge 2 commits into
Open
Conversation
f94eae7 to
1470f31
Compare
Contributor
|
We can implement REST Catalog in this PR too. This way we can have a global perspective. |
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
Support Spark replace-table flows for Paimon tables while preserving table history where possible.
This change adds staged replace support for
REPLACE TABLEandCREATE OR REPLACE TABLE ... AS SELECT, using truncate plus schema replacement for compatible FileStore tables so old snapshots remain available for time travel. It also falls back to drop-and-create when the source or target is not a Paimon table, handles SparkGenericCatalog provider checks, and documents the Spark SQL behavior.Follow-up TODOs:
Tests
Added coverage for catalog-level replace table, Spark SQL replace table, create-or-replace-as-select, incompatible schema replacement, table existence errors, provider/table type fallback, and time-travel reads after replace.