Fix: Add a category for metadata-only changes#2752
Merged
izeigerman merged 1 commit intomainfrom Jun 7, 2024
Merged
Conversation
3e2f678 to
61c290d
Compare
tobymao
approved these changes
Jun 7, 2024
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.
Coupling metadata and forward-only changes was a design mistake.
The forward-only category has a bunch of implications on how data is computed and reused. For example, table deployability, data previews, etc decisions are directly linked to this category.
However, none of these features apply to metadata changes. I've already seen quite a few unexpected behaviors related to the fact that metadata updates were categorized as forward-only which led to redundant computations in both dev and prod.
This update introduces a new category dedicated specifically to metadata-only changes.