You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Madhan Neethiraj (JIRA)" <ji...@apache.org> on 2016/04/29 07:48:13 UTC

[jira] [Created] (RANGER-960) Service-def update does not preserve the order in which permissions are listed

Madhan Neethiraj created RANGER-960:
---------------------------------------

             Summary: 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


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)