[
https://issues.apache.org/jira/browse/RANGER-4948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated RANGER-4948:
-------------------------------------
Attachment: RANGER-4948.patch
> optimize use of tries in GDS policy engine
> -------------------------------------------
>
> Key: RANGER-4948
> URL: https://issues.apache.org/jira/browse/RANGER-4948
> Project: Ranger
> Issue Type: Sub-task
> Components: plugins
> Affects Versions: 3.0.0
> Reporter: Madhan Neethiraj
> Assignee: Madhan Neethiraj
> Priority: Major
> Fix For: 3.0.0
>
> Attachments: RANGER-4948.patch
>
>
> In GDS data model, a data-share consists of a bunch of resources
> (databae/table/column/path/..) from a given service & security-zone.
> In GDS policy engine implementation, each data-share instance has its own
> resource-tries which are used to efficiently determine if a resource is part
> of a data-share instance. To find data-shares for a resource, GDS policy
> engine would perform as many trie lookup as the number of total data-shares.
> Trie lookups can be minimized by having all resources across data-shares in a
> resource-tries set. This will help improve the performance and memory
> requirements, especially when working with large number of data-share
> instances.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
