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-23.1: screl: Add IndexID as a attr of UniqueWithoutIndex element #100535

Merged
merged 1 commit into from
Apr 4, 2023

Conversation

blathers-crl[bot]
Copy link

@blathers-crl blathers-crl bot commented Apr 3, 2023

Backport 1/1 commits from #99858 on behalf of @Xiang-Gu.

/cc @cockroachdb/release


Previously, ALTER TABLE stmt where we add column/drop column/alter PK and adding a unique without index is problematic in that the it can succeed even when there are duplicate values. We already had a dep rule that enforces the new primary index to be backfilled before we validate the constraint against it. Unfortunately, this rule is not enforced on unique without index constraint because IndexID was not a attr of it. This commit fixes this.

Fixes #99281
Epic: None
Release note (bug fix): Fixed a bug in v23.1 in the declarative schema changer where unique without index can be incorrectly added in tables with duplicate values if it's with a ADD/DROP COLUMN in one ALTER TABLE statement.


Release justification: bug fix

Previously, in ALTER TABLE stmt where we add column/drop column/alter PK
and adding a unique without index is problematic in that the it can
succeed even when there are duplicate values. We already had a dep rule
that enforces the new primary index to be backfilled before we validate
the constraint against it. Unfortunately, this rule is not enforced on
unique without index constraint because IndexID was not a attr of it.
This commit fixes this.

Release note (bug fix): Fixed a bug in v23.1 in the declarative schema
changer where unique without index can be incorrectly added in tables
with duplicate values if it's with a ADD/DROP COLUMN in one ALTER TABLE
statement.
@blathers-crl blathers-crl bot requested review from a team and ajwerner April 3, 2023 22:43
@blathers-crl blathers-crl bot force-pushed the blathers/backport-release-23.1-99858 branch from 3416adf to d670c5c Compare April 3, 2023 22:43
@blathers-crl blathers-crl bot added the blathers-backport This is a backport that Blathers created automatically. label Apr 3, 2023
@blathers-crl
Copy link
Author

blathers-crl bot commented Apr 3, 2023

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 the O-robot Originated from a bot. label Apr 3, 2023
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@rafiss rafiss merged commit 02800ab into release-23.1 Apr 4, 2023
@rafiss rafiss deleted the blathers/backport-release-23.1-99858 branch April 4, 2023 17:26
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