[PROTOTYPE][DO_NOT_MERGE] Streaming write schema evolution#55279
Open
johanl-db wants to merge 2 commits intoapache:masterfrom
Open
[PROTOTYPE][DO_NOT_MERGE] Streaming write schema evolution#55279johanl-db wants to merge 2 commits intoapache:masterfrom
johanl-db wants to merge 2 commits intoapache:masterfrom
Conversation
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
1 participant
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?
Path-finding: attempting to automatically evolve the schema of the sink during streaming writes when the sink table reports capability
AUTOMATIC_SCHEMA_EVOLUTIONThis is a crude prototype and doesn't consider implications that evolving the sink schema may have on streaming semantics.
There's also no user-surface to enable schema evolution on a stream today. Delta uses for example
.option("mergeSchema", "true"), but Spark itself doesn't provide an a user surface for schema evolution. In this change, we assume that a connector implementation will intercept theWriteToMicroBatchDataSourcenode to enable schema evolution on it as needed