ddl: fix return duplicate schema version during multi-schema change#39093
ddl: fix return duplicate schema version during multi-schema change#39093ti-chi-bot merged 11 commits intopingcap:masterfrom
Conversation
|
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. DetailsReviewer can indicate their review by submitting an approval review. |
ddl/multi_schema_change.go
Outdated
| ver, err = w.runDDLJob(d, t, &proxyJob) | ||
| sub.FromProxyJob(&proxyJob, ver) | ||
| proxyJobVer, err := w.runDDLJob(d, t, &proxyJob) | ||
| if !proxyJob.MultiSchemaInfo.SkipVersion { |
There was a problem hiding this comment.
| if !proxyJob.MultiSchemaInfo.SkipVersion { | |
| if !schemaVersionGenerated { |
There was a problem hiding this comment.
The schemaVersionGenerated here always equal to true.
There was a problem hiding this comment.
Improve it by another way, please check again.
|
/merge |
|
This pull request has been accepted and is ready to merge. DetailsCommit hash: a5ac738 |
TiDB MergeCI notify✅ Well Done! New fixed [2] after this pr merged.
|
What problem does this PR solve?
Issue Number: close #39090
Problem Summary: multi-schema change will return same non-zero version in some scenarios which block MDL forever. We should prevent it.
What is changed and how it works?
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.