Skip to content

materialize: adds a new event to denote a breaking schema change#113

Merged
vroldanbet merged 1 commit intomainfrom
materialize-breaking-schema-change-event
Jul 4, 2024
Merged

materialize: adds a new event to denote a breaking schema change#113
vroldanbet merged 1 commit intomainfrom
materialize-breaking-schema-change-event

Conversation

@vroldanbet
Copy link
Copy Markdown
Contributor

A breaking schema changes require recomputing the snapshot to rebuild the Materialize index, and in turn once this is ready, the consumer will have to rebuild their own indexes. This event is added to differentiate between "schema changed" and "index ready after schema changed" events.

A breaking schema changes require recomputing the snapshot
to rebuild the Materialize index, and in turn once
this is ready, the consumer will have to rebuild their
own indexes. This event is added to differentiate between
"schema changed" and "index ready after schema changed" events.
@vroldanbet vroldanbet self-assigned this Jul 3, 2024
Copy link
Copy Markdown
Member

@josephschorr josephschorr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@vroldanbet vroldanbet merged commit 338339b into main Jul 4, 2024
@vroldanbet vroldanbet deleted the materialize-breaking-schema-change-event branch July 4, 2024 11:21
@github-actions github-actions bot locked and limited conversation to collaborators Jul 4, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants