hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5304) Pluggable split key policy
Date Thu, 02 Feb 2012 01:17:53 GMT

    [ https://issues.apache.org/jira/browse/HBASE-5304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13198427#comment-13198427

Lars Hofhansl commented on HBASE-5304:

@Jesse: Thanks for the comments.
* Good point on making PrefixSplitKeyPolicy it's own class. I'll do that. Need to make it
a bit nicer then. Or I can add a section to the HBase book (reference guide) with PrefixSplitKeyPolicy
as an example.
* The splitKey is always validated against the region before the actual split. If it is not
valid you get an error message (see HRegion.checkSplit and SplitTransaction.prepare) and the
split is not performed. Falling back to the default instead might invalidate other assumptions
that the application code had based on the provided SplitPolicy. Generally I see this as a
server extension. If you wanted to call System.exit() from the code you can, and it'll kill
your server on every split :)
* RegionSplitPolicy is already optionally loaded per table as well as per configuration (see

I think shell support would be for generally for setting HTableDescriptor values. I have some
ideas, but some refactoring would be needed to get it right, I'd rather do that in another

> 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


View raw message