Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F15A211D30 for ; Wed, 23 Apr 2014 17:01:46 +0000 (UTC) Received: (qmail 37737 invoked by uid 500); 23 Apr 2014 17:01:38 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 37454 invoked by uid 500); 23 Apr 2014 17:01:28 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 37355 invoked by uid 99); 23 Apr 2014 17:01:25 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Apr 2014 17:01:25 +0000 Date: Wed, 23 Apr 2014 17:01:25 +0000 (UTC) From: "ramkrishna.s.vasudevan (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-10916) [VisibilityController] Stackable ScanLabelGenerators MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-10916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13978452#comment-13978452 ] ramkrishna.s.vasudevan commented on HBASE-10916: ------------------------------------------------ +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 > Priority: Critical > Fix For: 0.99.0, 0.98.2 > > Attachments: HBASE-10916.patch, HBASE-10916_V2.patch, HBASE-10916_V3.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)