[
https://issues.apache.org/jira/browse/HBASE-10916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13976622#comment-13976622
]
Hadoop QA commented on HBASE-10916:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12641196/HBASE-10916.patch
against trunk revision .
ATTACHMENT ID: 12641196
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified tests.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:red}-1 javac{color}. The patch appears to cause mvn compile goal to
fail.
{color:red}-1 findbugs{color}. The patch appears to cause Findbugs
(version 1.3.9) to fail.
{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:red}-1 site{color}. The patch appears to cause mvn site goal to
fail.
{color:red}-1 core tests{color}. The patch failed these unit tests:
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/9357//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/9357//console
This message is automatically generated.
> [VisibilityController] Stackable ScanLabelGenerators
> ----------------------------------------------------
>
> Key: HBASE-10916
> URL: https://issues.apache.org/jira/browse/HBASE-10916
> Project: HBase
> Issue Type: Improvement
> Reporter: Andrew Purtell
> Assignee: Anoop Sam John
> Priority: Critical
> Fix For: 0.99.0, 0.98.2
>
> Attachments: HBASE-10916.patch
>
>
> The ScanLabelGenerator is used by the VisibilityController to assemble the
> effective label set for a user in the RPC context before processing any
> request. Currently only one implementation of this interface can be
> installed, although which implementation to use can be specified in the site
> file. Instead it should be possible to stack multiple implementations of this
> component the same way we do coprocessors, installed with explicit priority
> with ties broken by a counter, where those implementations installed later in
> the chain have an opportunity to modify the pending effective label set.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
