include dynamic columns for wildcard query #17462
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Return dynamic columns like MATERIALIZED / ALIAS for wildcard query when switches
asterisk_include_materialized_columns
andasterisk_include_alias_columns
are turned on.Detailed description / Documentation draft:
Previously for wildcard query like
SELECT * FROM <table>
, ALIAS/MATERIALIZED dynamic columns will not be included.Adding switches
asterisk_include_materialized_columns
andasterisk_include_alias_columns
to include these dynamic columns for wildcard query respectively. By default, these 2 switches are false for backward compatibility.Information about CI checks: https://clickhouse.tech/docs/en/development/continuous-integration/