-
Notifications
You must be signed in to change notification settings - Fork 7.7k
add allow_part_offset_column_in_projections setting #85372
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
Conversation
Workflow [PR], commit [c30f27a] Summary: ❌
|
If we truly need this guard, it would be better implemented as a MergeTree setting, similar to |
{ | ||
if (projection.with_parent_part_offset) | ||
{ | ||
if (!(*getSettings())[MergeTreeSetting::allow_part_offset_column_in_projections]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this should also check projections for new_metadata
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, you are right. I have added a test for that.
Cherry pick #85372 to 25.5: add allow_part_offset_column_in_projections setting
Cherry pick #85372 to 25.6: add allow_part_offset_column_in_projections setting
Cherry pick #85372 to 25.7: add allow_part_offset_column_in_projections setting
I want to make
allow_part_offset_column_in_projections=0
for25.6
andallow_part_offset_column_in_projections=1
for newer releases.release 25.6 has a bug #85314
The fix is big and it is not backported.
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes into CHANGELOG.md):
forbid using
_part_offset
column in projection in releases until it is stabilized.Documentation entry for user-facing changes