[
https://issues.apache.org/jira/browse/RANGER-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15307544#comment-15307544
]
rangerqa commented on RANGER-1004:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12807093/RANGER-1004.patch
against master revision bc63484.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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/226//testReport/
Console output:
https://builds.apache.org/job/PreCommit-RANGER-Build/226//console
This message is automatically generated.
> Remove need to set access type for column masking, row filtering in Ranger UI
> -----------------------------------------------------------------------------
>
> Key: RANGER-1004
> URL: https://issues.apache.org/jira/browse/RANGER-1004
> Project: Ranger
> Issue Type: Bug
> Components: admin
> Affects Versions: 0.6.0
> Reporter: Gautam Borad
> Assignee: Gautam Borad
> Priority: Minor
> Fix For: 0.6.0
>
> Attachments: RANGER-1004.patch
>
>
> Currently, the UI for row level filtering, column masking: the user needs to
> explicitly choose access type while setting up a policy in the UI. The access
> type has only one choice, "select"
> It seems very redundant. Suggestion to keep "select" as default access type
> whenever someone is creating a policy.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)