Cherry pick #85904 to 25.3: Fix logical error on creating table as s3Cluster() in Replicated database#85945
Conversation
Fix logical error on creating table as `s3Cluster()` in Replicated database
|
Dear @thevar1able, @KochetovNicolai, the PR is not updated for 1d1h0m27s. Please, either resolve the conflicts, or close it to finish the backport process of #85904 |
|
Dear @thevar1able, @KochetovNicolai, the PR is not updated for 1d0h58m27s. Please, either resolve the conflicts, or close it to finish the backport process of #85904 |
|
Dear @thevar1able, @KochetovNicolai, the PR is not updated for 1d1h1m16s. Please, either resolve the conflicts, or close it to finish the backport process of #85904 |
|
Dear @thevar1able, @KochetovNicolai, the PR is not updated for 1d0h0m3s. Please, either resolve the conflicts, or close it to finish the backport process of #85904 |
|
Dear @thevar1able, @KochetovNicolai, the PR is not updated for 1d0h1m23s. Please, either resolve the conflicts, or close it to finish the backport process of #85904 |
|
Dear @thevar1able, @KochetovNicolai, the PR is not updated for 1d0h0m27s. Please, either resolve the conflicts, or close it to finish the backport process of #85904 |
…rypick/25.3/85904
Original pull-request #85904
Do not merge this PR manually
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.
Troubleshooting
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 pull-request for
pr-backports-createdlabel, and delete if it's presented thereThe PR source
The PR is created in the CI job