[
https://issues.apache.org/jira/browse/HBASE-5304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13198348#comment-13198348
]
Lars Hofhansl commented on HBASE-5304:
--------------------------------------
I don't have much of a preference one way or the other.
Just that we have need for controlling "what key should we split at" to be able
to co-locate certain parts of the data that belong to the same tenant...
Note that RegionSplitPolicy already determines the split point, that part was
not just not extensible and did not work correctly for forced-splits.
This is a small change to make the existing functionality more useful.
Not opposed separating the two. In a different jira?
> 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
