[ 
https://issues.apache.org/jira/browse/RANGER-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Madhan Neethiraj updated RANGER-371:
------------------------------------
    Description: Policy search API does not seem to use the given resource 
values (like table=xyz&column=abc). This results in the UI to show incorrect 
list of policies when resource filters are specified. For example, give a HDFS 
repository hadoopdev, containing 2 policies - one for "/finance/\*" and another 
for "/hr/\*". When the user specified filter "path:/finance/\*", only the 1st 
policy should be returned. However, currently both policies are returned.  
(was: Policy search API does not seem to use the given resource values (like 
table=xyz&column=abc). This results in the UI to show incorrect list of 
policies when resource filters are specified. For example, give a HDFS 
repository hadoopdev, containing 2 policies - one for "/finance/*" and another 
for "/hr/*". When the user specified filter "path:/finance/*", only the 1st 
policy should be returned. However, currently both policies are returned.)

> Policy search does not filter based on resource values
> ------------------------------------------------------
>
>                 Key: RANGER-371
>                 URL: https://issues.apache.org/jira/browse/RANGER-371
>             Project: Ranger
>          Issue Type: Bug
>          Components: admin
>    Affects Versions: 0.5.0
>            Reporter: Madhan Neethiraj
>            Assignee: Madhan Neethiraj
>
> Policy search API does not seem to use the given resource values (like 
> table=xyz&column=abc). This results in the UI to show incorrect list of 
> policies when resource filters are specified. For example, give a HDFS 
> repository hadoopdev, containing 2 policies - one for "/finance/\*" and 
> another for "/hr/\*". When the user specified filter "path:/finance/\*", only 
> the 1st policy should be returned. However, currently both policies are 
> returned.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to