[
https://issues.apache.org/jira/browse/RANGER-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15263655#comment-15263655
]
rangerqa commented on RANGER-960:
---------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12801399/0001-RANGER-960-service-def-update-should-preserve-the-pe.patch
against master revision 3fa3de2.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
+1 checkstyle. The patch generated 0 code style errors.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-RANGER-Build/192//testReport/
Console output:
https://builds.apache.org/job/PreCommit-RANGER-Build/192//console
This message is automatically generated.
> 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
> 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)
