[
https://issues.apache.org/jira/browse/RANGER-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16580151#comment-16580151
]
Abhay Kulkarni edited comment on RANGER-2188 at 8/21/18 10:44 PM:
------------------------------------------------------------------
Commit details:
master:
[https://git-wip-us.apache.org/repos/asf?p=ranger.git;a=commit;h=466edce78bd97fbf87b17cd5e3e85c40834b0556]
https://git-wip-us.apache.org/repos/asf?p=ranger.git;a=commit;h=07076c18e527606c116a560ff08c171ee39d90bb
was (Author: abhayk):
Commit details:
master:
https://git-wip-us.apache.org/repos/asf?p=ranger.git;a=commit;h=466edce78bd97fbf87b17cd5e3e85c40834b0556
> Support multiple threads to build Trie and on-lookup post-setup for Trie nodes
> ------------------------------------------------------------------------------
>
> Key: RANGER-2188
> URL: https://issues.apache.org/jira/browse/RANGER-2188
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Affects Versions: master
> Reporter: Abhay Kulkarni
> Assignee: Abhay Kulkarni
> Priority: Major
> Fix For: master
>
>
> Time for building a Trie index for resources may become a bottleneck when
> dealing with large number of resources. It is desirable to build different,
> non-overlapping parts of Trie structure using multiple threads to reduce
> overall build time if configured to do so.
> Also, instead of building out all Trie nodes completely (that is, by
> propagating wildcard evaluators all the way to all leaves of Trie tree) at
> the initialization time, it is optimal to do so as a Trie-Node is accessed
> for the first time during resource lookup.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
