-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
ddl: add check for max index key length when alter modify/change column #11220
ddl: add check for max index key length when alter modify/change column #11220
Conversation
/run-all-tests |
Codecov Report
@@ Coverage Diff @@
## master #11220 +/- ##
===========================================
Coverage 81.6297% 81.6297%
===========================================
Files 423 423
Lines 91719 91719
===========================================
Hits 74870 74870
Misses 11549 11549
Partials 5300 5300 |
…0/tidb into check-index-column-len
/run-all-tests |
1 similar comment
/run-all-tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/rebuild |
/run-all-tests |
/run-all-tests |
/run-all-tests tidb-test=pr/858 |
/run-integration-common-test tidb-test=pr/858 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/run-all-tests |
/run-all-tests tidb-test=pr/858 |
/run-all-tests tidb-test=pr/858 |
/run-common-test tidb-test=pr/858 |
/run-integration-common-test tidb-test=pr/858 |
What is the negative result of exceeding the max length(3072) in TiDB? Do we need to be compatible with MySQL's weakness? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rest LGTM
Co-Authored-By: Tanner <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@crazycs520 Please cherry-pick this pr to release-3.0. |
cherry pick to release-2.1 failed |
cherry pick to release-3.0 in PR #11395 |
It seems that, not for sure, we failed to cherry-pick this commit to release-2.1. Please comment '/run-cherry-picker' to try to trigger the cherry-picker if we did fail to cherry-pick this commit before. @crazycs520 PTAL. |
…mn (pingcap#11220) Signed-off-by: crazycs520 <[email protected]>
What problem does this PR solve?
MySQL
TiDB
What is changed and how it works?
Check List
Tests
Code changes
Side effects
Related changes