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

schemachanger: Annotate all tables if ALTER TABLE IF EXISTS on non-existent table #99839

Merged

Conversation

Xiang-Gu
Copy link
Contributor

Previously, if table t does not exist, ALTER TABLE IF EXISTS t will only mark t as non-existent. This is inadequate because for stmt like ALTER TABLE IF EXISTS t ADD FOREIGN KEY REFERENCES t_other we will not touch t_other and the validation logic will later complain that t_other is not fully resolved nor marked as non-existent. This commit fixes it by marking all tables in this ALTER TABLE stmt as non-existent if the t is non-existent, so we can pass the validation.

Fixes issues discovered in #99185
Epic: None

…uited

Previously, if table `t` does not exist, `ALTER TABLE IF EXISTS t` will
only mark `t` as non-existent. This is inadequate because for stmt
like `ALTER TABLE IF EXISTS t ADD FOREIGN KEY REFERENCES t_other` we
will not touch `t_other` and the validation logic will later complain
that `t_other` is not fully resolved nor marked as non-existent. This
commit fixes it by marking all tables in this ALTER TABLE stmt as
non-existent if the `t` is non-existent, so we can pass the validation.
@Xiang-Gu Xiang-Gu requested a review from a team March 28, 2023 18:16
@Xiang-Gu Xiang-Gu requested a review from a team as a code owner March 28, 2023 18:16
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@rafiss rafiss added the backport-23.1.x Flags PRs that need to be backported to 23.1 label Mar 28, 2023
Copy link
Collaborator

@rafiss rafiss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thank you!

@Xiang-Gu
Copy link
Contributor Author

TFTR!

bors r+

@craig
Copy link
Contributor

craig bot commented Mar 28, 2023

Build failed (retrying...):

@craig
Copy link
Contributor

craig bot commented Mar 29, 2023

Build failed (retrying...):

@craig
Copy link
Contributor

craig bot commented Mar 29, 2023

Build failed (retrying...):

@craig
Copy link
Contributor

craig bot commented Mar 30, 2023

Build succeeded:

@blathers-crl
Copy link

blathers-crl bot commented Mar 30, 2023

Encountered an error creating backports. Some common things that can go wrong:

  1. The backport branch might have already existed.
  2. There was a merge conflict.
  3. The backport branch contained merge commits.

You might need to create your backport manually using the backport tool.


error setting reviewers, but backport branch blathers/backport-release-23.1-99839 is ready: POST https://api.github.com/repos/cockroachdb/cockroach/pulls/100011/requested_reviewers: 422 Reviews may only be requested from collaborators. One or more of the teams you specified is not a collaborator of the cockroachdb/cockroach repository. []

Backport to branch 23.1.x failed. See errors above.


🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-23.1.x Flags PRs that need to be backported to 23.1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants