Skip to content

adapter: Force migrations when upgrading from dev version - #36251

Merged
def- merged 1 commit into
MaterializeInc:mainfrom
def-:pr-force-migration
Apr 28, 2026
Merged

def- merged 1 commit into
MaterializeInc:mainfrom
def-:pr-force-migration

Conversation

@def-

@def- def- commented Apr 24, 2026 •

Copy link
Copy Markdown
Contributor

@def-
def- requested review from antiguru and ggevay April 24, 2026 16:09
@def-
def- requested a review from a team as a code owner April 24, 2026 16:09
@def-
def- requested a review from aljoscha April 25, 2026 00:41
@def-
def- marked this pull request as draft April 25, 2026 00:41
@def-
def- force-pushed the pr-force-migration branch from 8bdc7fa to df6253b Compare April 25, 2026 01:19
@def-
def- marked this pull request as ready for review April 25, 2026 03:11
@def-
def- requested a review from ggevay April 28, 2026 10:39
@def-
def- force-pushed the pr-force-migration branch from df6253b to e920acc Compare April 28, 2026 13:04
@def-
def- force-pushed the pr-force-migration branch from e920acc to dbe039c Compare April 28, 2026 13:32
@def-
def- merged commit 6aacf14 into MaterializeInc:main Apr 28, 2026
120 checks passed
@def-
def- deleted the pr-force-migration branch April 28, 2026 14:36
def- added a commit that referenced this pull request May 21, 2026
Forced dev->dev evolution (#36251) iterates every Table/MV in the
durable catalog, including brand-new builtins whose shards have not been
registered yet. In read-only replicas this trips the "missing shard ID
for builtin" bail in migrate_evolve_one, since the leader has not yet
allocated the shard. Filter them out: there is nothing to evolve or
replace for an object that does not yet exist in persist.

Fixes https://linear.app/materializeinc/issue/SQL-282

Follow-up to #36251

Nightly run: https://buildkite.com/materialize/nightly/builds/16506

Co-authored-by: Claude Opus 4.7 (1M context) <[email protected]>
bobbyiliev pushed a commit to bobbyiliev/materialize that referenced this pull request May 21, 2026
…#36668)

Forced dev->dev evolution (MaterializeInc#36251) iterates every Table/MV in the
durable catalog, including brand-new builtins whose shards have not been
registered yet. In read-only replicas this trips the "missing shard ID
for builtin" bail in migrate_evolve_one, since the leader has not yet
allocated the shard. Filter them out: there is nothing to evolve or
replace for an object that does not yet exist in persist.

Fixes https://linear.app/materializeinc/issue/SQL-282

Follow-up to MaterializeInc#36251

Nightly run: https://buildkite.com/materialize/nightly/builds/16506

Co-authored-by: Claude Opus 4.7 (1M context) <[email protected]>
antiguru pushed a commit to antiguru/materialize that referenced this pull request May 25, 2026
…#36668)

Forced dev->dev evolution (MaterializeInc#36251) iterates every Table/MV in the
durable catalog, including brand-new builtins whose shards have not been
registered yet. In read-only replicas this trips the "missing shard ID
for builtin" bail in migrate_evolve_one, since the leader has not yet
allocated the shard. Filter them out: there is nothing to evolve or
replace for an object that does not yet exist in persist.

Fixes https://linear.app/materializeinc/issue/SQL-282

Follow-up to MaterializeInc#36251

Nightly run: https://buildkite.com/materialize/nightly/builds/16506

Co-authored-by: Claude Opus 4.7 (1M context) <[email protected]>
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.

3 participants