[
https://issues.apache.org/jira/browse/RANGER-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar updated RANGER-4060:
-----------------------------------
Description:
Both the tables x_user_module_perm and x_group_module_perm contain the column
module_id which should have a NON NULL constraint. Also, the pair \{user_id,
module_id} in table x_user_module_perm and the pair \{group_id, module_id} in
table x_group_module_perm should be unique.
Using rest apis in place, it's possible to create entries in the tables with
module_id as NULL which needs to be avoided.
was:Both the tables x_user_module_perm and x_group_module_perm contain the
column module_id which should have a NON NULL constraint. Also, the pair
\{user_id, module_id} in table x_user_module_perm and the pair \{group_id,
module_id} in table x_group_module_perm should be unique.
> Schema change for x_user_module_perm and x_group_module_perm tables
> -------------------------------------------------------------------
>
> Key: RANGER-4060
> URL: https://issues.apache.org/jira/browse/RANGER-4060
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Reporter: Abhishek Kumar
> Priority: Major
>
> Both the tables x_user_module_perm and x_group_module_perm contain the column
> module_id which should have a NON NULL constraint. Also, the pair \{user_id,
> module_id} in table x_user_module_perm and the pair \{group_id, module_id} in
> table x_group_module_perm should be unique.
> Using rest apis in place, it's possible to create entries in the tables with
> module_id as NULL which needs to be avoided.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
