-
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: support table placement option #27799
ddl: support table placement option #27799
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. Reviewer can indicate their review by submitting an approval review. |
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.
I just noticed that in the RFC:
You can not use both a placement policy and direct assignment. If you alter specify both in a CREATE TABLE or ALTER TABLE an error will be returned.
Maybe we should not override?
0d4c729
to
b0df2ee
Compare
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.
Looks like format is still broken.
/merge |
This pull request has been accepted and is ready to merge. Commit hash: d2fc288ce2e8945c1fbfafb485371dfc445dacc1
|
/run-check_dev_2 |
2 similar comments
/run-check_dev_2 |
/run-check_dev_2 |
Signed-off-by: ailinkid <[email protected]>
Signed-off-by: ailinkid <[email protected]>
Signed-off-by: ailinkid <[email protected]>
Signed-off-by: ailinkid <[email protected]>
Signed-off-by: ailinkid <[email protected]>
Signed-off-by: ailinkid <[email protected]>
a32c9b3
to
c6b5550
Compare
/merge |
This pull request has been accepted and is ready to merge. Commit hash: b4a7c08
|
/run-check_dev_2 |
Signed-off-by: ailinkid [email protected]
What problem does this PR solve?
Issue Number: particial close #26581
What is changed and how it works?
1: Support create table with placement options, which could be direct placement options or placement policy.
When both this two exists, placement policy take the priority to take effect in the schedule of PD.
2: Since we move the policyInfo into the parser, so we change the reference source to parser.
Check List
Tests
Release note