[ https://issues.apache.org/jira/browse/ACCUMULO-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13573728#comment-13573728 ]
Josh Elser commented on ACCUMULO-164: ------------------------------------- bq. Maybe the most useful, and general, thing we could do to provide users the most utility to select families for a locality group, is to allow users to inject a user-defined hash function (maybe in JEXL?) to bin families into discrete localities by the arbitrary method of their choosing? I'm not sure how much I like the idea of tying some external dependency to the core implementation, but having a very clear interface may reduce ambiguity. Keeping a locality group defined as a set of column families helps, where a prefix match on column families defines a set of column families, and thus locality group. bq. If implemented, I think documentation should be sufficient to address all of my concerns. The main thing is just make it clear that the feature is used to select multiple column families, so that it's not implied that families with variability are the same "family". The API treats non-equal families as distinct, and that's how we should discuss them. Very well said. bq. Accumulo did not extend it. The Big Table paper described a locality group as a set of column families. In Hbase each col fam is a locality group. Accumulo may differ from Big Table in that it allows user to change what col fams are in a locality group, not sure about this. It also differs by having a default locality group. Thanks for the clarification, [~kturner]. > 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