Cherry pick #54211 to 23.8: Refactor parameterized view & add support for new analyzer#66650
Conversation
…elect part with default values
…with_analyzer Refactor parameterized view & add support for new analyzer
robot-clickhouse-ci-2
added
pr-cherrypick
|
Dear @novikd, @kssenii, @SmitaRKulkarni, the PR is not updated for 1d25h3m5s. Please, either resolve the conflicts, or close it to finish the backport process of #54211 |
|
Dear @novikd, @kssenii, @SmitaRKulkarni, the PR is not updated for 1d24h0m0s. Please, either resolve the conflicts, or close it to finish the backport process of #54211 |
|
Dear @novikd, @kssenii, @SmitaRKulkarni, the PR is not updated for 1d24h13m37s. Please, either resolve the conflicts, or close it to finish the backport process of #54211 |
|
Dear @novikd, @kssenii, @SmitaRKulkarni, the PR is not updated for 1d24h42m45s. Please, either resolve the conflicts, or close it to finish the backport process of #54211 |
|
Dear @novikd, @kssenii, @SmitaRKulkarni, the PR is not updated for 1d24h0m55s. Please, either resolve the conflicts, or close it to finish the backport process of #54211 |
…d6bf02275a54b3d887794610a9e
robot-ch-test-poll4
deleted the
cherrypick/23.8/a3c34a7cc2342d6bf02275a54b3d887794610a9e
branch
7 participants
Original pull-request #54211
This pull-request is a first step of an automated backporting.
It contains changes similar to calling
git cherry-picklocally.If you intend to continue backporting the changes, then resolve all conflicts if any.
Otherwise, if you do not want to backport them, then just close this pull-request.
The check results does not matter at this step - you can safely ignore them.
Note
This pull-request will be merged automatically. Please, do not merge it manually (but if you accidentally did, nothing bad will happen).
Troubleshooting
If the PR was manually reopened after being closed
If this PR is stuck (i.e. not automatically merged after one day), check #54211 for
pr-backports-createdlabel and delete it.Manually merging will do nothing. The
pr-backports-createdlabel prevents the original PR #54211 from being processed.If the conflicts were resolved in a wrong way
If this cherry-pick PR is completely screwed by a wrong conflicts resolution, and you want to recreate it:
pr-cherrypicklabel from the PRYou also need to check the original PR #54211 for
pr-backports-created, and delete if it's presented there