-
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
*: Implementing information_schema.placement_rules #27478
Conversation
But not filling it with correct data and columns are still not fully defined.
[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. |
Signed-off-by: ailinkid <314806019@qq.com>
Signed-off-by: ailinkid <314806019@qq.com>
Signed-off-by: ailinkid <314806019@qq.com>
…into is.placement_rules
TODO: Schema level TODO: Partition level TODO: Add tests for privileges on Schema and Table level
} | ||
} | ||
} */ | ||
if table.DirectPlacementOpts == nil { |
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.
Do we need to output the relationship between named placement policies and tables?
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 think that is what the SHOW PLACEMENT [FOR ...]
is for. As I understand the requirements for information_schema.placement_rules is to find all definitions of placement rules, not necessary which objects are using the named policies. But I also don't know how you would get the full list of objects using a specific PLACEMENT POLICY.
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.
That's right - my intention in the proposal was to include those that have policies.
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
// Get global PLACEMENT POLICIES | ||
// Currently no privileges needed for seeing global PLACEMENT POLICIES! |
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.
Whatever, the PR looks good to me. Maybe should merge it first.
For the problem, I think a new dynamic priv is enough. I could argue that there will be only one super DBA responsible for placement configurations, because only if you know all clusters can you schedule it better.
The problem only happens when there are two sets of settings, e.g. one in cn
and another in us
... But I think it can be effectively filtered using tricks like name: cn_policy_1
.
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 guess it is prepared since partition support is added.
/merge |
This pull request has been accepted and is ready to merge. Commit hash: a491ae5
|
@mjonss: Your PR was out of date, I have automatically updated it for you. At the same time I will also trigger all tests for you: /run-all-tests If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
What problem does this PR solve?
Issue Number: partly close #26681, still missing Direct placement for Partitions (not yet implemented)
Problem Summary:
What is changed and how it works?
What's Changed:
How it Works:
Check List
Tests
Side effects
Documentation
Release note