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.1: opt: fix crdb_internal.decode_plan_gist to work with unknown index #84726

Merged
merged 1 commit into from
Jul 22, 2022

Conversation

blathers-crl[bot]
Copy link

@blathers-crl blathers-crl bot commented Jul 20, 2022

Backport 1/1 commits from #84682 on behalf of @rytaft.

/cc @cockroachdb/release


Release note (bug fix): crdb_internal.decode_plan_gist will no longer
produce an internal error when it is used to decode a plan gist for which
no schema information is available.


Release justification: Fix internal error when decoding plan gists

Release note (bug fix): crdb_internal.decode_plan_gist will no longer
produce an internal error when it is used to decode a plan gist for which
no schema information is available.
@blathers-crl blathers-crl bot requested a review from a team as a code owner July 20, 2022 16:32
@blathers-crl blathers-crl bot force-pushed the blathers/backport-release-22.1-84682 branch from 5ba1b36 to c3dc767 Compare July 20, 2022 16:32
@blathers-crl
Copy link
Author

blathers-crl bot commented Jul 20, 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?

@blathers-crl blathers-crl bot added blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot. labels Jul 20, 2022
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@rytaft rytaft merged commit a84b36b into release-22.1 Jul 22, 2022
@rytaft rytaft deleted the blathers/backport-release-22.1-84682 branch July 22, 2022 16:10
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.

3 participants