Created 06-20-2017 11:25 AM
this question might sound stupid, But to validate whether i am creating correct policy in ranger or not, I guess this may be mandatory.
I have observed this in ranger 0.7, if we create a policy on a database which is not available in HDFS, policy gets created. Only check is on Group or User for which permission is granted. let me explain more using an example:
1. Database : random (NA in HDFS)
2. Table : random
3. Column : random
4. Group : public (valid linux group)
5. Permission : select
policy will get created using these inputs, although Database, table and column are not available.
So, In order to validate i would like to access hive metadata (Hive and ranger metadata available in MySQL). and check whether the policy is getting created on correct database or not. Please note that i am creating policies using rest API by feeding in an excel. this excel can be erroneous because it gets created manually.
Thank you in Advance,
Subash
Created 06-20-2017 01:50 PM
In many scenarios, users might want to create the ranger policies in advance before the actual resources are created. So policy creation cannot be blocked based on resources. Moreover, wildcards are supported in policies.
Created 06-20-2017 01:50 PM
In many scenarios, users might want to create the ranger policies in advance before the actual resources are created. So policy creation cannot be blocked based on resources. Moreover, wildcards are supported in policies.