Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 1 Apr 2014 17:23:17 +0000 (UTC)
From: "ramkrishna.s.vasudevan (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12705863.1396336372974.45334.1396372997779@arcas>
In-Reply-To: <JIRA.12705863.1396336372974@arcas>
References: <JIRA.12705863.1396336372974@arcas>
Subject: [jira] [Commented] (HBASE-10883) Restrict the universe of labels
 and authorizations
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

ramkrishna.s.vasudevan commented on HBASE-10883:
------------------------------------------------

bq.We better keep the validation at server side? 
I thought HConstants would help in client side validation. I thought of unifying but decided not to as I thought better to be client side, just on creation of Authorization object.

> Restrict the universe of labels and authorizations
> --------------------------------------------------
>
>                 Key: HBASE-10883
>                 URL: https://issues.apache.org/jira/browse/HBASE-10883
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 0.98.1
>            Reporter: Andrew Purtell
>             Fix For: 0.99.0, 0.98.2
>
>         Attachments: HBASE-10883.patch, HBASE-10883_1.patch
>
>
> Currently we allow any string as visibility label or request authorization. However as seen on HBASE-10878, we accept for authorizations strings that would not work if provided as labels in visibility expressions. We should throw an exception at least in cases where someone tries to define or use a label or authorization including visibility expression operators '&', '|', '!', '(', ')'.


--
This message was sent by Atlassian JIRA
(v6.2#6252)