*: support auto_random table option (#16750) #16813
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
/run-all-tests |
sre-bot
added
sig/sql-infra
ghost
requested a review
from
sre-bot
requested review from
bb7133,
crazycs520,
djshow832,
SunRunAway,
tangenta and
zimulala
|
don't worry, the releated parser hasn't been cherry-picked, wait for a while |
|
the linked parser is in pingcap/parser#831 |
zimulala
added
the
status/can-merge
|
/run-all-tests |
|
/merge |
|
/run-all-tests |
|
@sre-bot merge failed. |
AilinKid
force-pushed
the
release-4.0-7b25ce0d948d
branch
from
d8f61e5
to
7edf0f3
Compare
|
/run-all-tests |
|
/run-all-tests |
|
/run-integration-copr-test |
1 similar comment
|
/run-integration-copr-test |
|
/run-check_dev |
zimulala
approved these changes
Apr 27, 2020
This was referenced May 11, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
cherry-pick #16750 to release-4.0
What problem does this PR solve?
Problem Summary: support
auto_random_basetable optionWhat is changed and how it works?
How it Works:
After this table option:
We can do the auto_random rebase by
alter table xxx auto_random_base = numAlso we can specify the initial auto_random base by
create table t xxx(xxx) auto_random_base = numRelated changes
pingcap/docs/pingcap/docs-cn:Check List
Tests
Release note
support auto_random table option for rebase auto_random allocator