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-21.2: sql: do not include inaccessible columns in information_schema.columns #73540

Merged
merged 1 commit into from
Dec 30, 2021

Conversation

blathers-crl[bot]
Copy link

@blathers-crl blathers-crl bot commented Dec 7, 2021

Backport 1/1 commits from #73447 on behalf of @mgartner.

/cc @cockroachdb/release


This commit omits inaccessible columns from the
information_schema.columns table. Inaccessible columns are also
excluded in SHOW COLUMNS due to its reliance on
information_schema.columns.

Fixes #70505

Release note (bug fix): Internal columns created by the system to
support expression indexes are now omitted from the output of SHOW COLUMNS statements and the information_schema.columns table.


Release justification: This is a minor bug fix for expression indexes, a
new feature in 21.2.

@blathers-crl blathers-crl bot force-pushed the blathers/backport-release-21.2-73447 branch from e8846a9 to 222dfd5 Compare December 7, 2021 00:46
@blathers-crl blathers-crl bot requested a review from rafiss December 7, 2021 00:46
@blathers-crl
Copy link
Author

blathers-crl bot commented Dec 7, 2021

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 blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot. labels Dec 7, 2021
@cockroach-teamcity
Copy link
Member

This change is Reviewable

SELECT * FROM [SHOW COLUMNS FROM t] ORDER BY column_name
----
column_name data_type is_nullable column_default generation_expression indices is_hidden
a INT8 true NULL · {t_pkey} false
Copy link
Collaborator

Choose a reason for hiding this comment

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

looks like t_pkey needs to be changed to primary for the backport

@github-actions
Copy link

Reminder: it has been 3 weeks please merge or close your backport!

This commit omits inaccessible columns from the
`information_schema.columns` table. Inaccessible columns are also
excluded in `SHOW COLUMNS` due to its reliance on
`information_schema.columns`.

Fixes #70505

Release note (bug fix): Internal columns created by the system to
support expression indexes are now omitted from the output of `SHOW
COLUMNS` statements and the `information_schema.columns` table.
@mgartner mgartner force-pushed the blathers/backport-release-21.2-73447 branch from 222dfd5 to e420f0f Compare December 29, 2021 14:49
@mgartner mgartner merged commit dc72c17 into release-21.2 Dec 30, 2021
@mgartner mgartner deleted the blathers/backport-release-21.2-73447 branch December 30, 2021 18:29
@blathers-crl
Copy link
Author

blathers-crl bot commented Dec 30, 2021

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 getting backport branch release-pr-activity: GET https://api.github.com/repos/cockroachdb/cockroach/branches/release-pr-activity: 404 Branch not found []

Backport to branch pr-activity failed. See errors above.


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

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. no-backport-pr-activity O-robot Originated from a bot.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants