-
Notifications
You must be signed in to change notification settings - Fork 312
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
feat(Ranger): add a default database policy name for legacy table #1507
feat(Ranger): add a default database policy name for legacy table #1507
Conversation
dsn::replication::update_app_env_rpc rpc(std::move(req), LPC_USE_RANGER_ACCESS_CONTROL); | ||
_meta_svc->get_server_state()->set_app_envs(rpc); | ||
LOG_AND_RETURN_NOT_OK(ERROR, rpc.response().err, "set_app_envs failed."); | ||
break; |
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.
Is it possible that a table match multiple 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.
Yes, next patch will solve this problem: i will add a new data structure to record all matching policies
What problem does this PR solve?
#1054
What is changed and how does it work?
legacy_table_database_mapping_policy_name
,the legacy table (the tables which are created before Ranger ACL enabled) will be
matched to the database named
legacy_table_database_mapping_policy_name
for ACL.
A new configuration is added:
[ranger] + legacy_table_database_mapping_policy_name = __default__