[
https://issues.apache.org/jira/browse/HBASE-5304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13198419#comment-13198419
]
Jesse Yates commented on HBASE-5304:
------------------------------------
@Lars:
I was thinking you could make PrefixSplitKeyPolicy its own full class in the
test package. This would help make it more obvious to people that it is around.
Also, some docs on it's usage would be awesome.
I'm also worried that the test for the split policy needs to be run on a
minicluster to ensure that we "do the right thing" for messed up splits. This
goes into Ted's point of about what if we put in a bad policy. My first
inclination on that was that we fall back on the default split policy and push
and angry message (possibly tying that into the log), rather than just bailing
(taking a preference here for uptime)
Excuse the ignorance here, nbut since the policy is loaded just based on the
configuration of the RS, is there a way to make it just table based? Or will it
be global across the cluster? If the former, then I think a little more work
needs to be put into make that work. Also, shell support?
> 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
