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

Keith Turner commented on ACCUMULO-241:
---------------------------------------

I like the idea of quoting.  We keep the current white list.  If the user wants 
to use something outside of that list, they have to quote it.  For example if a 
user wanted to use the label foo.bar, then they would need to do 'foo.bar'.  I 
think this has the following benefits:

 * backwards compatible with existing data
 * allows users to use whatever characters they like in their labels
 * give us the flexibility to use additional characters in the language in the 
future
 * is human readable

Would just need an escape mechanism for quote, could do the standard two quotes.

One drawback I can think of is that users can make labels that look like 
expressions, like 'A&B'.  This is the type of thing that a computer has no 
issues with, but it may mislead a person. 
                
> Visibility labels should blacklist non-ASCII characters instead of 
> whitelisting select ASCII characters
> -------------------------------------------------------------------------------------------------------
>
>                 Key: ACCUMULO-241
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-241
>             Project: Accumulo
>          Issue Type: Improvement
>    Affects Versions: 1.3.5
>            Reporter: John Vines
>              Labels: visibility
>             Fix For: 1.3.6
>
>
> We currently whitelist our visibility labels to only allow alphanumerics and 
> a few select delimiting characters. While we strive for human-readable 
> labels, we should instead utilize a blacklist approach where we disallow 
> parentheses, ampersands, pipes, and any non-ASCII characters. This will 
> provide users with more flexibility in labeling, while still sticking to 
> human readability.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to