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
Fix_max_query_size_for_kql_compound_operator: #60534
Fix_max_query_size_for_kql_compound_operator: #60534
Conversation
Fix the issue of max_query_size for kql compound operator like mv-expand this fix another use case for PR 59626
Hi @antaljanosbenjamin , can you review this PR, this fixed another use case for kql operators like mv-expand (for #59626) Thanks |
This is an automated comment for commit 8d106f6 with description of existing statuses. It's updated for the latest CI running ❌ Click here to open a full report in a separate page Successful checks
|
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.
The changes looks great, only a tiny change for better readability.
…etter readability
Tests:
|
6e58161
into
ClickHouse:master
…e045f7cabe170582d1df068a42acc1 Cherry pick #60534 to 23.12: Fix_max_query_size_for_kql_compound_operator:
…045f7cabe170582d1df068a42acc1 Cherry pick #60534 to 24.1: Fix_max_query_size_for_kql_compound_operator:
…045f7cabe170582d1df068a42acc1 Cherry pick #60534 to 24.2: Fix_max_query_size_for_kql_compound_operator:
Backport #60534 to 24.2: Fix_max_query_size_for_kql_compound_operator:
Backport #60534 to 23.12: Fix_max_query_size_for_kql_compound_operator:
Backport #60534 to 24.1: Fix_max_query_size_for_kql_compound_operator:
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Fix the issue of
max_query_size
for KQL compound operator like mv-expand. Related to #59626.