[
https://issues.apache.org/jira/browse/HBASE-5304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13198288#comment-13198288
]
Todd Lipcon commented on HBASE-5304:
------------------------------------
I'm a little skeptical of combining this with RegionSplitPolicy -- but perhaps
that class needs a better name. In my mind, the decision of "when should we
split?" is orthogonal to "what key should we split at". Of course there is some
interaction between the two - eg if the split policy says we should split, but
the region has only one row, we can't actually do so... but for the common case
they seem to be separate decisions.
For example, there's a proposal (which I never got around to implementing) of a
split policy which would make small regions "early on" as a table's created,
and then once a table has many regions, start to up the region size
automatically. That should work whether you do the current mid-point splits or
you do a custom split policy that avoids "entity groups".
> Pluggable split key policy
> --------------------------
>
> Key: HBASE-5304
> URL: https://issues.apache.org/jira/browse/HBASE-5304
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Fix For: 0.94.0
>
> Attachments: 5304-v4.txt
>
>
> We need a way to specify custom policies to determine split keys.
--
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
