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: planner: fix print valid sql in show create view #82196

Merged
merged 1 commit into from Jun 2, 2022

Conversation

blathers-crl[bot]
Copy link

@blathers-crl blathers-crl bot commented Jun 1, 2022

Backport 1/1 commits from #82026 on behalf of @likzn.

/cc @cockroachdb/release


When we create materialized view .. then use show create table in the past, it will not print keyword of materialized. So when entering show_create_clauses to use desc.MaterializedView() to judge whether is materialized view and print valid sql.

Fixes #80829

Release note (bug fix): The output of SHOW CREATE VIEW now properly includes the keyword MATERIALIZED for materialized views.


Release justification: bug fix

When we create materialized view .. then use show create table in the past, it will not print keyword of materialized. So when entering show_create_clauses to use desc.MaterializedView() to judge whether is materialized view and print valid sql.

Fixes #80829

Release note (bug fix): The output of SHOW CREATE VIEW now properly includes the keyword MATERIALIZED for materialized views.
@blathers-crl blathers-crl bot requested a review from a team June 1, 2022 03:46
@blathers-crl blathers-crl bot force-pushed the blathers/backport-release-22.1-82026 branch from 6dbfec1 to 48686e4 Compare June 1, 2022 03:46
@blathers-crl blathers-crl bot requested a review from a team as a code owner June 1, 2022 03:46
@blathers-crl
Copy link
Author

blathers-crl bot commented Jun 1, 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 requested a review from knz June 1, 2022 03:46
@blathers-crl blathers-crl bot added blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot. labels Jun 1, 2022
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@rafiss rafiss self-requested a review June 1, 2022 03:46
@rafiss rafiss merged commit 1ac45cf into release-22.1 Jun 2, 2022
@rafiss rafiss deleted the blathers/backport-release-22.1-82026 branch June 2, 2022 17:18
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.

None yet

4 participants