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 CF9D0112F7 for ; Wed, 13 Aug 2014 05:38:12 +0000 (UTC) Received: (qmail 61898 invoked by uid 500); 13 Aug 2014 05:38:12 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 61856 invoked by uid 500); 13 Aug 2014 05:38:12 -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 61842 invoked by uid 99); 13 Aug 2014 05:38:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Aug 2014 05:38:12 +0000 Date: Wed, 13 Aug 2014 05:38:12 +0000 (UTC) From: "Anoop Sam John (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-11438) [Visibility Controller] Support UTF8 character as Visibility Labels 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-11438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14095172#comment-14095172 ] Anoop Sam John commented on HBASE-11438: ---------------------------------------- bq.Only when parsing visibility expressions will we need to differentiate between the characters that make up a label identifier and operators in the expression. There we require operator-like chars in the identifier to be quoted Yes there to differentiate, we will quote it. What I was thinking is when a label contains these special op characters, user has to quote it. Not just in CellVisibility but also in Authorizations. If the auth label is quoted we do NO validation. But when it is not, we can validate the presence of special op chars. And so HBASE-10883 still present. This was in my mind though not so strong about. If you both feel that is not really needed I will also go with you. > [Visibility Controller] Support UTF8 character as Visibility Labels > ------------------------------------------------------------------- > > Key: HBASE-11438 > URL: https://issues.apache.org/jira/browse/HBASE-11438 > Project: HBase > Issue Type: Improvement > Components: security > Affects Versions: 0.98.4 > Reporter: ramkrishna.s.vasudevan > Assignee: ramkrishna.s.vasudevan > Fix For: 0.98.6 > > Attachments: HBASE-11438_v1.patch, HBASE-11438_v2.patch, HBASE-11438_v3.patch, HBASE-11438_v4.patch, HBASE-11438_v5.patch, HBASE-11438_v6.patch, HBASE-11438_v7.patch, HBASE-11438_v8.patch, HBASE-11438_v9.patch > > > This would be an action item that we would be addressing so that the visibility labels could have UTF8 characters in them. Also allow the user to use a client supplied API that allows to specify the visibility labels inside double quotes such that UTF8 characters and cases like &, |, ! and double quotes itself could be specified with proper escape sequence. Accumulo too provides one such API in the client side. -- This message was sent by Atlassian JIRA (v6.2#6252)