[
https://issues.apache.org/jira/browse/RANGER-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15264888#comment-15264888
]
Madhan Neethiraj edited comment on RANGER-960 at 4/29/16 11:21 PM:
-------------------------------------------------------------------
Fix committed to master:
http://git-wip-us.apache.org/repos/asf/incubator-ranger/commit/1fc84ff6
Fix committed to ranger-0.5:
http://git-wip-us.apache.org/repos/asf/incubator-ranger/commit/0fef5d86
was (Author: madhan.neethiraj):
Fix committed to master:
http://git-wip-us.apache.org/repos/asf/incubator-ranger/commit/1fc84ff6
> Service-def update does not preserve the order in which permissions are listed
> ------------------------------------------------------------------------------
>
> Key: RANGER-960
> URL: https://issues.apache.org/jira/browse/RANGER-960
> Project: Ranger
> Issue Type: Bug
> Components: admin
> Affects Versions: 0.5.0, 0.6.0
> Reporter: Madhan Neethiraj
> Assignee: Madhan Neethiraj
> Fix For: 0.6.0
>
> Attachments:
> 0001-RANGER-960-service-def-update-should-preserve-the-pe.patch
>
>
> Consider a Hive policy - the policy UI lists the permissions in the following
> order: select, update, create, drop, alter, index, lock, all.
> After an update to Hive service-def (for example to add a custom-condition),
> the policy UI lists the permission in a different order.
> For a better user experience and consistency, service-def updates should
> preserve the ordering of the permissions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
