[
https://issues.apache.org/jira/browse/RANGER-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16630633#comment-16630633
]
Velmurugan Periasamy edited comment on RANGER-2218 at 10/4/18 3:35 PM:
-----------------------------------------------------------------------
master -
[https://git-wip-us.apache.org/repos/asf?p=ranger.git;a=commit;h=f2e148abbe473a5fa23419373897082a3bf63974]
ranger-1 -
[https://git-wip-us.apache.org/repos/asf?p=ranger.git;a=commit;h=b7c84df7f792acd7ed8ec0654b6b969b3a407a67]
ranger-1.1 -
[https://git-wip-us.apache.org/repos/asf?p=ranger.git;a=commit;h=4fe455699a8de3894c5bebc5d7b88d1fb93d97e3]
ranger-0.7 -
https://git-wip-us.apache.org/repos/asf?p=ranger.git;a=commit;h=ac456e84c848cf3378ee97c95b4a381bbdd6f703
was (Author: vperiasamy):
master -
[https://git-wip-us.apache.org/repos/asf?p=ranger.git;a=commit;h=f2e148abbe473a5fa23419373897082a3bf63974]
ranger-1 -
[https://git-wip-us.apache.org/repos/asf?p=ranger.git;a=commit;h=b7c84df7f792acd7ed8ec0654b6b969b3a407a67]
ranger-1.1 -
[https://git-wip-us.apache.org/repos/asf?p=ranger.git;a=commit;h=4fe455699a8de3894c5bebc5d7b88d1fb93d97e3]
ranger-0.7 -
https://github.com/apache/ranger/commit/ac456e84c848cf3378ee97c95b4a381bbdd6f703
> Service-Definition update should not allow updates to names of resources,
> access-types, conditions or data-masks
> -----------------------------------------------------------------------------------------------------------------
>
> Key: RANGER-2218
> URL: https://issues.apache.org/jira/browse/RANGER-2218
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
> Affects Versions: master
> Reporter: Abhay Kulkarni
> Assignee: Sailaja Polavarapu
> Priority: Major
> Fix For: 0.7.2, 2.0.0, 1.1.1, 1.2.0
>
> Attachments:
> 0001-RANGER-2218-Added-validations-for-names-duing-servic.patch
>
>
> Updates to service definitions should not allow updating names of the
> following components:
> * Resources
> * Access types
> * Policy conditions
> * Data Masks
> In general, these updates are seldom needed and can be avoided by careful
> design of service definition. Also, with a de-normalized database schema for
> storing policies, it is expensive and inefficient to maintain and lookup
> mapping from internal IDs to names for each of these components. By not
> allowing updates to these names, there is no need to maintain ( or reference)
> such mappings after updating (or reading) policy when using de-normalized
> database schema.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
