[
https://issues.apache.org/jira/browse/HBASE-11438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087558#comment-14087558
]
ramkrishna.s.vasudevan commented on HBASE-11438:
------------------------------------------------
bq.But we should validate (like we did in past)
Then the validation should check for double quotes and allow that. But I don't
feel that would be needed. Because then we should actually parse the string
rewrite the string without quotes. Same applies with authorizations also.
Other argument I would suggest is that if we are allowing everything in the
addLabels and authorizations what is there to be validated? And the point to
see here is that in the addlabels and authorizations there is no expression
that we are trying to build. So for using &,!,| should be made simple IMO.
> [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
>
>
> 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)
