[
https://issues.apache.org/jira/browse/RANGER-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Velmurugan Periasamy updated RANGER-2203:
-----------------------------------------
Fix Version/s: (was: master)
2.0.0
> Review and update database schema for ranger policies to minimize database
> queries/updates
> ------------------------------------------------------------------------------------------
>
> Key: RANGER-2203
> URL: https://issues.apache.org/jira/browse/RANGER-2203
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
> Affects Versions: master
> Reporter: Abhay Kulkarni
> Priority: Major
> Fix For: 2.0.0
>
>
> Currently, ranger policies are fully normalized and stored in a multiple
> Relational database tables. There is a performance overhead incurred when
> retrieving a ranger policy, as multiple database accesses are required to
> fully reconstruct it. This is significant when there are large ranger
> policies (that is, the number of resources addressed by the policy is large),
> and/or when there is a large number of ranger policies in an installation.
> This Jira tracks alternate design of database schema, where a policy is
> stored in a de-normalized way, in its entirely, in one database table
> (preferably as a JSON string).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
