[
https://issues.apache.org/jira/browse/HBASE-5304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13197532#comment-13197532
]
Lars Hofhansl commented on HBASE-5304:
--------------------------------------
@Ted
* Region too big... That is why we make this pluggable. If you cannot manage
your region size then do not write a pluggable split key policy. This is like a
coprocessor calling System.exit(). You need to know what you are doing.
The whole point of this is to not put any specific split key policy into the
trunk, so that trunk does not have to be changed and folks can hood up their
own policy.
Surely you will not argue that nobody will ever want to change the split key
policy. We do the same for the existing split policy (what if that leads to too
big regions?)
* Will publish the next version of RB. Good point. I'll actually remove the
PrefixSplitKeyPolicy, which should not be part of the patch. Instead we'll add
documentation of SplitKeyPolicy on how to add a new policy.
* DefaultSplitKeyPolicy is not configurable. So passing in the config might be
confusing.
> 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.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
