-
Notifications
You must be signed in to change notification settings - Fork 558
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
refactor(engine): apply MT migration in chunks #16139
Conversation
Backport failed for Please cherry-pick the changes locally. git fetch origin main
git worktree add -d .worktree/backport-16139-to-main origin/main
cd .worktree/backport-16139-to-main
git checkout -b backport-16139-to-main
ancref=$(git merge-base 1e32958c3318f4c48c930479b03d39f0136c129f d6a6aa35fc8715581fdbe6ab270d40950bcf6fd0)
git cherry-pick -x $ancref..d6a6aa35fc8715581fdbe6ab270d40950bcf6fd0 |
Backport failed for Please cherry-pick the changes locally. git fetch origin stable/8.4
git worktree add -d .worktree/backport-16139-to-stable/8.4 origin/stable/8.4
cd .worktree/backport-16139-to-stable/8.4
git checkout -b backport-16139-to-stable/8.4
ancref=$(git merge-base 1e32958c3318f4c48c930479b03d39f0136c129f d6a6aa35fc8715581fdbe6ab270d40950bcf6fd0)
git cherry-pick -x $ancref..d6a6aa35fc8715581fdbe6ab270d40950bcf6fd0 |
We might not have merged the other parts yet 😄 Let's try after they are merged in the respective branches |
/backport |
Successfully created backport PR for |
Successfully created backport PR for |
Description
This PR applies the migration transaction split to all multi tenancy migrations in 8.3. No new tests added mostly because we've shown this fix only mitigates things, so we will do that in a follow up PR.
Related issues
related to #14975
Definition of Done
Not all items need to be done depending on the issue and the pull request.
Code changes:
backport stable/1.3
) to the PR, in case that fails you need to create backports manually.Testing:
Documentation:
Other teams:
If the change impacts another team an issue has been created for this team, explaining what they need to do to support this change.
Please refer to our review guidelines.