ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Velmurugan Periasamy (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (RANGER-1199) Optimize tag-download to include only tags that have policies
Date Tue, 17 Jan 2017 18:53:26 GMT

    [ https://issues.apache.org/jira/browse/RANGER-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15826599#comment-15826599
] 

Velmurugan Periasamy commented on RANGER-1199:
----------------------------------------------

Additional patch from https://reviews.apache.org/r/55151/ is committed to master branch. 

https://git-wip-us.apache.org/repos/asf?p=incubator-ranger.git;a=commit;h=387aaf8a96070629a9e1a3014060731fa343f207

> Optimize tag-download to include only tags that have policies
> -------------------------------------------------------------
>
>                 Key: RANGER-1199
>                 URL: https://issues.apache.org/jira/browse/RANGER-1199
>             Project: Ranger
>          Issue Type: Improvement
>          Components: admin
>    Affects Versions: 0.6.0, 0.6.1
>            Reporter: Madhan Neethiraj
>            Assignee: Abhay Kulkarni
>             Fix For: 0.7.0
>
>
> For the calls to download tags from plugins, Ranger Admin returns all the service-resources
that have one or more tags associated. This can be optimized to include only service-resources
that have tags for which policies exists.
> For example, if tag-based policies exists for tags PII and PCI, Ranger Admin should return
service-resources that are associated with PII or PCI tags only; any service-resource that
is not associated with either of these tags should be excluded. In addition to reducing the
size of the tag-download, this can improve policy-engine performance by not having to deal
with tags that don't have policies.



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

Mime
View raw message