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

schemachange: more informative dependent job descriptions #48163

Merged
merged 1 commit into from
Apr 30, 2020

Conversation

spaskob
Copy link
Contributor

@spaskob spaskob commented Apr 29, 2020

DROP xxx statements have cascading effects of causing sequences, indexes
and views being dropped as well. We should name the jobs that execute them
accordingly so that it is clear to users that they are connected to the
inital DROP statement.

Fixes #35051.

Release note (bug fix): Better distinguish between the delete jobs for
columns and dependent jobs for deleting indices, views and sequences. In the
current state clients were confused why more than 1 job was created from
a DROP COLUMN statement.

@spaskob spaskob requested a review from thoszhang April 29, 2020 15:53
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@blathers-crl
Copy link

blathers-crl bot commented Apr 29, 2020

❌ The GitHub CI (Cockroach) build has failed on 08c9bed2.

🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is otan.

Copy link
Contributor

@thoszhang thoszhang left a comment

Choose a reason for hiding this comment

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

Should we backport to 20.1?

Reviewed 4 of 4 files at r1.
Reviewable status: :shipit: complete! 0 of 0 LGTMs obtained

Copy link
Contributor Author

@spaskob spaskob left a comment

Choose a reason for hiding this comment

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

yes, that make sense

Reviewable status: :shipit: complete! 0 of 0 LGTMs obtained

`DROP xxx` statements have cascading effects of causing sequences, indexes
and views being dropped as well. We should name the jobs that execute them
accordingly so that it is clear to users that they are connected to the
inital `DROP` statement.

Fixes cockroachdb#35051.

Release note (bug fix): Better distinguish between the delete jobs for
columns and dependent jobs for deleting indices, views and sequences. In the
current state clients were confused why more than 1 job was created from
a `DROP COLUMN` statement.
@spaskob
Copy link
Contributor Author

spaskob commented Apr 30, 2020

bors r+

@craig
Copy link
Contributor

craig bot commented Apr 30, 2020

Build succeeded

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

schema: Better distinguish between the delete jobs for columns and indices
3 participants