-
Notifications
You must be signed in to change notification settings - Fork 97
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
explicitly call EnsurePullability while adding tables #1298
base: main
Are you sure you want to change the base?
Conversation
}) | ||
if err := ensurePullabilityFuture.Get(ctx, nil); err != nil { | ||
w.logger.Error("failed to ensure pullability for additional tables: ", err) | ||
return err |
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.
Can this be return nil
?
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.
processCDCFlowConfigUpdates
return value should not be aborting whole workflow. Any flow config update error should result in an error being reported to user in some way, & then being ignored. Then this can remain return err
c9dd1c0
to
97a23c7
Compare
|
The UI for dynamic table addition should prevent tables that we cannot mirror via CDC [no primary key + replident != full] to be selected. However, we end up using the signal for adding tables sometimes, and currently there is no check in this codepath.
Invoking
EnsurePullability
explicitly to guard against this.