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

Andrew Purtell commented on HBASE-10916:
----------------------------------------

The patch did apply to the precommit builds, odd.

{noformat}
======================================================================
======================================================================
    Applying patch.
======================================================================
======================================================================


Going to apply patch with: /usr/bin/patch -p0
(Stripping trailing CRs from patch.)
patching file 
hbase-server/src/main/java/org/apache/hadoop/hbase/security/visibility/LabelFilteringScanLabelGenerator.java
(Stripping trailing CRs from patch.)
patching file 
hbase-server/src/main/java/org/apache/hadoop/hbase/security/visibility/TestVisibilityLabelsWithSLGStack.java
(Stripping trailing CRs from patch.)
patching file 
hbase-server/src/main/java/org/apache/hadoop/hbase/security/visibility/VisibilityController.java
(Stripping trailing CRs from patch.)
patching file 
hbase-server/src/main/java/org/apache/hadoop/hbase/security/visibility/VisibilityUtils.java
{noformat}

But there's an issue with Windows CRLFs again Anoop. 


> [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)

Reply via email to