-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set breaking change to false when connection is fixed #20315
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@@ -654,6 +654,11 @@ protected static ConnectionUpdate toConnectionPatch(final WebBackendConnectionUp | |||
final List<UUID> finalOperationIds) { | |||
final ConnectionUpdate connectionPatch = new ConnectionUpdate(); | |||
|
|||
if (webBackendConnectionPatch.getSyncCatalog() != null) { | |||
// the user has updated their sync catalog, so there is no breaking change |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we check that all the change are now not breaking?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this was considered in the tech design but it requires getting the source schema and calculating a diff again. what do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is a simpler way of doing it based on FE validations (they can't update an invalid sync catalog), but maybe it's better for us to re-validate here too
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just realized the env variable won't work if we do this, since we're marking connections as broken even in the absence of the env variable. so I'll have to update to fetch the most recent actor catalog and do a diff to check whether it's broken
3feaca1
to
d45e124
Compare
When users update their connection's sync catalog after there is a breaking schema change, the breaking_change field should be set to false