Repository navigation
fix(hcl): allow materialized view patches to replace to_table - #239
Merged
Merged
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
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.
Materialized views with different destinations across compositions previously required a full
override, duplicating their query and columns. Allowpatch_materialized_viewto replaceto_tablewhile inheriting the other fields.Update layer serialization and decompose to preserve and generate destination-only patches, and document the new field.
Validation: non-live tests across
internal,cmd,config, andtestpass, plusgo vet ./.... Regression coverage includes inherited query/columns, patch ordering, empty destination validation, and decompose round trips.Fixes #238