ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abhay Kulkarni (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (RANGER-2203) Review and update database schema for ranger policies to minimize database queries/updates
Date Thu, 18 Oct 2018 19:46:00 GMT

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

Abhay Kulkarni updated RANGER-2203:
-----------------------------------
    Attachment: RANGER-2203-RANGER-2219-for-master.patch

> 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: 0.7.0, master
>            Reporter: Abhay Kulkarni
>            Assignee: Abhay Kulkarni
>            Priority: Major
>             Fix For: 0.7.2, 2.0.0
>
>         Attachments: RANGER-2203-RANGER-2219-for-master.patch
>
>
> 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)

Mime
View raw message