[ 
https://issues.apache.org/jira/browse/HBASE-11438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14074354#comment-14074354
 ] 

Hadoop QA commented on HBASE-11438:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12657821/HBASE-11438_v3.patch
  against trunk revision .
  ATTACHMENT ID: 12657821

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 12 new 
or modified tests.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  The javadoc tool did not generate any 
warning messages.

    {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 lineLengths{color}.  The patch does not introduce lines 
longer than 100

  {color:green}+1 site{color}.  The mvn site goal succeeds with this patch.

     {color:red}-1 core tests{color}.  The patch failed these unit tests:
                       
org.apache.hadoop.hbase.security.visibility.TestExpressionParser

Test results: 
https://builds.apache.org/job/PreCommit-HBASE-Build/10188//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/10188//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/10188//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/10188//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/10188//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/10188//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/10188//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/10188//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/10188//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/10188//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/10188//console

This message is automatically generated.

> [Visibility Controller] Support UTF8 character as Visibility Labels
> -------------------------------------------------------------------
>
>                 Key: HBASE-11438
>                 URL: https://issues.apache.org/jira/browse/HBASE-11438
>             Project: HBase
>          Issue Type: Improvement
>          Components: security
>    Affects Versions: 0.98.4
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>             Fix For: 0.98.5
>
>         Attachments: HBASE-11438_v1.patch, HBASE-11438_v2.patch, 
> HBASE-11438_v3.patch
>
>
> This would be an action item that we would be addressing so that the 
> visibility labels could have UTF8 characters in them.  Also allow the user to 
> use a client supplied API that allows to specify the visibility labels inside 
> double quotes such that UTF8 characters and cases like &, |, ! and double 
> quotes itself could be specified with proper escape sequence.  Accumulo too 
> provides one such API in the client side.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to