Cherry pick #49660 to 23.3: Fix reading from sparse columns after restart #60246
Conversation
Fix reading from sparse columns after restart
robot-clickhouse-ci-1
added
pr-cherrypick
|
Dear @alexey-milovidov, @CurtizJ, @kssenii, the PR is not updated for 1d24h2m43s. Please, either resolve the conflicts, or close it to finish the backport process of #49660 |
|
Dear @alexey-milovidov, @CurtizJ, @kssenii, the PR is not updated for 1d24h0m33s. Please, either resolve the conflicts, or close it to finish the backport process of #49660 |
|
Dear @alexey-milovidov, @CurtizJ, @kssenii, the PR is not updated for 1d24h59m4s. Please, either resolve the conflicts, or close it to finish the backport process of #49660 |
|
Dear @alexey-milovidov, @CurtizJ, @kssenii, the PR is not updated for 1d24h58m11s. Please, either resolve the conflicts, or close it to finish the backport process of #49660 |
|
Dear @alexey-milovidov, @CurtizJ, @kssenii, the PR is not updated for 1d24h3m22s. Please, either resolve the conflicts, or close it to finish the backport process of #49660 |
|
Dear @alexey-milovidov, @CurtizJ, @kssenii, the PR is not updated for 1d24h23m30s. Please, either resolve the conflicts, or close it to finish the backport process of #49660 |
|
Dear @alexey-milovidov, @CurtizJ, @kssenii, the PR is not updated for 1d24h4m13s. Please, either resolve the conflicts, or close it to finish the backport process of #49660 |
|
Dear @alexey-milovidov, @CurtizJ, @kssenii, the PR is not updated for 1d24h18m9s. Please, either resolve the conflicts, or close it to finish the backport process of #49660 |
|
Dear @alexey-milovidov, @CurtizJ, @kssenii, the PR is not updated for 1d24h10m45s. Please, either resolve the conflicts, or close it to finish the backport process of #49660 |
|
Dear @alexey-milovidov, @CurtizJ, @kssenii, the PR is not updated for 1d24h0m52s. Please, either resolve the conflicts, or close it to finish the backport process of #49660 |
|
Dear @alexey-milovidov, @CurtizJ, @kssenii, the PR is not updated for 1d24h59m18s. Please, either resolve the conflicts, or close it to finish the backport process of #49660 |
alexey-milovidov
added
the
close in a month if not active
…81493005e5d23f437c222e7f362
robot-clickhouse-ci-1
deleted the
cherrypick/23.3/4a4eb5b17100481493005e5d23f437c222e7f362
branch
Original pull-request #49660
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 #49660 for
pr-backports-createdlabel and delete it.Manually merging will do nothing. The
pr-backports-createdlabel prevents the original PR #49660 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 #49660 for
pr-backports-created, and delete if it's presented there