[
https://issues.apache.org/jira/browse/HBASE-10916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13961373#comment-13961373
]
Anoop Sam John edited comment on HBASE-10916 at 4/6/14 10:20 AM:
-----------------------------------------------------------------
bq.whether we should be calling these "ScanLabelGenerators" or
"ScanAuthsGenerators"
+1 for ScanAuthsGenerators. That would be a better name.
The conf we have named as
"hbase.regionserver.scan.visibility.label.generator.class" already.
was (Author: anoop.hbase):
bq.whether we should be calling these "ScanLabelGenerators" or
"ScanAuthsGenerators"
+1
> [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)
