[ 
https://issues.apache.org/jira/browse/HBASE-10916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Purtell updated HBASE-10916:
-----------------------------------

    Description: 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.  (was: 
The ScanLabelGenerator is used by the VisibilityController to assembly 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.)

> [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
>             Fix For: 0.99.0, 0.98.2
>
>
> 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