[
https://issues.apache.org/jira/browse/ACCUMULO-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13227645#comment-13227645
]
Keith Turner commented on ACCUMULO-164:
---------------------------------------
A prefix wildcard is a simple form of a range. One other thing we may want to
consider is simply having ranges. So the candidates for this ticket would be
prefix wildcards, suffix wildcards, and/or ranges. These can be all be
automatically verified as disjoint.
Is allowing this type of setting in locality group configuration worthwhile w/o
changing the scanner API? If we decided to allow prefix wildcards, then it
would be easy to create a locality group with millions of actual column
families. However there is no way on the client side to ask for everything in
that locality group without enumerating all possible column families. It may
not be possible to enumerate all possible columns families, therefore it may
not be possible to read an entire locality group. To remedy this the client
API and iterator API would need to be changed to allow specification of column
prefixes (or ranges, or column suffixes).
> 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
>
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
