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

Improve parser and schemadiff support for ALTER TABLE #10313

Merged
merged 2 commits into from
May 16, 2022

Conversation

dbussink
Copy link
Contributor

The parser logic for ALTER TABLE was not allowing for the INSTANT algorithm. This doesn't implement anything for instant DDL, but it specifically only allows parsing it.

Additionally, the new VISIBLE / INVISIBLE property on columns can be set using an ALTER TABLE ALTER COLUMN, so this is also added to the parser as well.

Lastly, this makes schemadiff work with such an ALTER TABLE statement. It doesn't generate these itself at this point, but implementing support for handling it is simple to add so this was done as well.

Related Issue(s)

Identified as part of #10203

Checklist

  • "Backport me!" label has been added if this change should be backported
  • Tests were added or are not required
  • Documentation was added or is not required

@dbussink dbussink added Type: Enhancement Logical improvement (somewhere between a bug and feature) Component: Query Serving release notes labels May 15, 2022
@github-actions
Copy link
Contributor

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

  • Ensure that the Pull Request has the correct release notes label. release notes none should only be used for PRs that are so trivial that they need not be included.
  • If a new flag is being introduced, review whether it is really needed. The flag names should be clear and intuitive (as far as possible), and the flag's help should be descriptive.

Bug fixes

  • There should be at least one unit or end-to-end test.
  • The Pull Request description should either include a link to an issue that describes the bug OR an actual description of the bug and how to reproduce, along with a description of the fix.

Non-trivial changes

  • There should be some code comments as to why things are implemented the way they are.

New/Existing features

  • Should be documented, either by modifying the existing documentation or creating new documentation.
  • New features should have a link to a feature request issue or an RFC that documents the use cases, corner cases and test cases.

Backward compatibility

  • Protobuf changes should be wire-compatible.
  • Changes to _vt tables and RPCs need to be backward compatible.
  • vtctl command output order should be stable and awk-able.

The parser logic for ALTER TABLE was not allowing for the INSTANT
algorithm. This doesn't implement anything for instant DDL, but it
specifically only allows parsing it.

Additionally, the new VISIBLE / INVISIBLE property on columns can be set
using an `ALTER TABLE ALTER COLUMN`, so this is also added to the parser
as well.

Lastly, this makes schemadiff work with such an ALTER TABLE statement.
It doesn't generate these itself at this point, but implementing support
for handling it is simple to add so this was done as well.

Signed-off-by: Dirkjan Bussink <d.bussink@gmail.com>
Signed-off-by: Dirkjan Bussink <d.bussink@gmail.com>
@shlomi-noach shlomi-noach merged commit 5b1746b into vitessio:main May 16, 2022
@dbussink dbussink deleted the parse-instant-algorithm branch May 16, 2022 08:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Query Serving Type: Enhancement Logical improvement (somewhere between a bug and feature)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants