Skip to content
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

release-22.2.0: backupccl: use the backup codec when inspecting spans in the backupManifest #90528

Merged
merged 1 commit into from
Oct 24, 2022

Conversation

blathers-crl[bot]
Copy link

@blathers-crl blathers-crl bot commented Oct 23, 2022

Backport 1/1 commits from #90477 on behalf of @msbutler.

/cc @cockroachdb/release


Informs #90475, #90474

Release note (bug fix): previously, during restore planning, the restoring cluster's codec was accidentally used to reason about spans in the backup manifest. When a backup was restored by a different tenant, two bugs described in #90475, #90474 could manifest. This patch fixes these bugs.


Release justification: bug fix

…nifest

Informs #90475, #90474

Release note (bug fix): previously, during restore planning, the restoring
cluster's codec was accidentally used to reason about spans in the backup
manifest. When a backup was restored by a different tenant, two bugs described
in #90475, #90474 could manifest. This patch fixes these bugs.
@blathers-crl blathers-crl bot requested review from a team as code owners October 23, 2022 22:30
@blathers-crl blathers-crl bot removed the request for review from a team October 23, 2022 22:30
@blathers-crl blathers-crl bot force-pushed the blathers/backport-release-22.2.0-90477 branch from db86613 to e153157 Compare October 23, 2022 22:30
@blathers-crl blathers-crl bot added blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot. labels Oct 23, 2022
@blathers-crl
Copy link
Author

blathers-crl bot commented Oct 23, 2022

Thanks for opening a backport.

Please check the backport criteria before merging:

  • Patches should only be created for serious issues or test-only changes.
  • Patches should not break backwards-compatibility.
  • Patches should change as little code as possible.
  • Patches should not change on-disk formats or node communication protocols.
  • Patches should not add new functionality.
  • Patches must not add, edit, or otherwise modify cluster versions; or add version gates.
If some of the basic criteria cannot be satisfied, ensure that the exceptional criteria are satisfied within.
  • There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way.
  • The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting).
  • New code is protected by a conditional check that is trivial to verify and ensures that it only runs for opt-in clusters.
  • The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.

Add a brief release justification to the body of your PR to justify this backport.

Some other things to consider:

  • What did we do to ensure that a user that doesn’t know & care about this backport, has no idea that it happened?
  • Will this work in a cluster of mixed patch versions? Did we test that?
  • If a user upgrades a patch version, uses this feature, and then downgrades, what happens?

@cockroach-teamcity
Copy link
Member

This change is Reviewable

@msbutler msbutler merged commit 78c93e2 into release-22.2.0 Oct 24, 2022
@msbutler msbutler deleted the blathers/backport-release-22.2.0-90477 branch October 24, 2022 12:55
@dt
Copy link
Member

dt commented Oct 24, 2022

note for docs: this shouldn't have a release note.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants