-
Notifications
You must be signed in to change notification settings - Fork 0
slack-19.0
: pre-backport v23 vtorc PR vitessio/vitess#17985
#635
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
base: slack-19.0
Are you sure you want to change the base?
Conversation
Signed-off-by: Tim Vaillancourt <tim@timvaillancourt.com>
Signed-off-by: Tim Vaillancourt <tim@timvaillancourt.com>
vtorc
: add support for dynamic enable/disable of ERS by keyspace/shardslack-19.0
: backport v22 vtorc PR vitessio/vitess#17985
slack-19.0
: backport v22 vtorc PR vitessio/vitess#17985slack-19.0
: pre-backport v23 vtorc PR vitessio/vitess#17985
|
||
defer unlock(&err) | ||
|
||
if req.Shard != "" && req.Shard != "-" { |
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.
I have seen single shard keyspaces referred to as shard 0
. Should that be included here?
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.
@ejortegau technically 0
is a single shard in the middle of the keyspace. And -
is actually referring to the entire shard range of the keyspace
So, no I believe this logic is correct as-is. Considering 0
to be a whole keyspace has consequences on splits
Description
Pre-backport upstream v23 PR vitessio#17985 in order to provide some test results to upstream
Related Issue(s)
vitessio#17985
Checklist
Deployment Notes