Add sync plan version 2#717
Merged
Merged
Conversation
🦋 Changeset detectedLatest commit: 861bb02 The changes in this PR will be included in the next version bump. This PR includes changesets to release 20 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
simolus3
force-pushed
the
sync-plan-versioning
branch
from
July 15, 2026 12:37
861bb02 to
56590b8
Compare
simolus3
marked this pull request as ready for review
July 15, 2026 12:57
stevensJourney
approved these changes
Jul 20, 2026
stevensJourney
left a comment
Collaborator
There was a problem hiding this comment.
The changes here look good to me.
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.
#703 introduced syntax exposing table and schema names to bucket data and parameter creators, a change that requires changes to the serialized form of sync plans.
Older service versions would not load these correctly, so they should reject those plans outright. The version field added to sync plans helps here, older services throw if it's not
1. This PR:2for sync plans, used when.schema(),.table_suffix()or.table_name()are used in an expression of the sync plan. Existing deployments not using the new row metadata functions are unaffected.By continuing to use plan version 1 where possible, we allow service downgrades as long as the new functions aren't used in sync plans (if there are, there's no way an older service could implement those streams either way).