Skip to content

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

Open
wants to merge 6 commits into
base: slack-19.0
Choose a base branch
from

Conversation

timvaillancourt
Copy link
Member

@timvaillancourt timvaillancourt commented Apr 9, 2025

Description

Pre-backport upstream v23 PR vitessio#17985 in order to provide some test results to upstream

Related Issue(s)

vitessio#17985

Checklist

  • "Backport to:" labels have been added if this change should be back-ported to release branches
  • If this change is to be back-ported to previous releases, a justification is included in the PR description
  • Tests were added or are not required
  • Did the new or modified tests pass consistently locally and on CI?
  • Documentation was added or is not required

Deployment Notes

@github-actions github-actions bot added this to the v19.0.7 milestone Apr 9, 2025
@timvaillancourt timvaillancourt changed the title vtorc: add support for dynamic enable/disable of ERS by keyspace/shard slack-19.0: backport v22 vtorc PR vitessio/vitess#17985 Apr 9, 2025
@timvaillancourt timvaillancourt self-assigned this Apr 9, 2025
@timvaillancourt timvaillancourt changed the title slack-19.0: backport v22 vtorc PR vitessio/vitess#17985 slack-19.0: pre-backport v23 vtorc PR vitessio/vitess#17985 Apr 9, 2025
Signed-off-by: Tim Vaillancourt <[email protected]>
Signed-off-by: Tim Vaillancourt <[email protected]>
Signed-off-by: Tim Vaillancourt <[email protected]>
@timvaillancourt timvaillancourt marked this pull request as ready for review April 9, 2025 13:34
@timvaillancourt timvaillancourt requested a review from a team as a code owner April 9, 2025 13:34

defer unlock(&err)

if req.Shard != "" && req.Shard != "-" {

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?

Copy link
Member Author

@timvaillancourt timvaillancourt Apr 16, 2025

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

Copy link

github-actions bot commented Jun 7, 2025

This PR is being marked as stale because it has been open for 30 days with no activity. To rectify, you may do any of the following:

  • Push additional commits to the associated branch.
  • Remove the stale label.
  • Add a comment indicating why it is not stale.

If no action is taken within 7 days, this PR will be closed.

@github-actions github-actions bot added the Stale label Jun 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants