[
https://issues.apache.org/jira/browse/ACCUMULO-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13570589#comment-13570589
]
Josh Elser commented on ACCUMULO-164:
-------------------------------------
I was thinking it would be easiest in the server implementation of the
createLocalityGroup (I forget if it's TableOpsImpl...) could perform the check
to ensure that there is no overlap. That should catch both the Java client,
Accumulo shell and proxy calls, no?
The way Keith explained it to me (and sorry if I butcher this description),
RFile would have to be modified from using a HashSet internally to track
locality groups to a trie. I'm not sure how much, if at all, prefix or suffix
(mutually exclusive) definitions makes things more difficult.
> Add support for wildcards/regexes in locality group setting.
> ------------------------------------------------------------
>
> Key: ACCUMULO-164
> URL: https://issues.apache.org/jira/browse/ACCUMULO-164
> Project: Accumulo
> Issue Type: Improvement
> Components: client, master, tserver
> Reporter: John Vines
> Fix For: 1.6.0
>
>
> We should look into adding the ability to specify locality group columns as
> either wildcarding or regexes. I'm unsure of the feasibility of this, hence
> the lack of fix date.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
