Skip to content

Fix: Add a category for metadata-only changes#2752

Merged
izeigerman merged 1 commit intomainfrom
fix-metadata-change-category
Jun 7, 2024
Merged

Fix: Add a category for metadata-only changes#2752
izeigerman merged 1 commit intomainfrom
fix-metadata-change-category

Conversation

@izeigerman
Copy link
Contributor

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.

@izeigerman izeigerman requested a review from a team June 6, 2024 22:29
@izeigerman izeigerman force-pushed the fix-metadata-change-category branch from 3e2f678 to 61c290d Compare June 6, 2024 22:40
@izeigerman izeigerman merged commit 25f4a77 into main Jun 7, 2024
@izeigerman izeigerman deleted the fix-metadata-change-category branch June 7, 2024 16:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants