[
https://issues.apache.org/jira/browse/HBASE-7748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13581634#comment-13581634
]
Robert Dyer commented on HBASE-7748:
------------------------------------
@Enis, perhaps a change in the data model would avoid this situation. However
to me, regardless of the data model, it appears that this behaviour is
non-optimal.
We select a split point (roughly the middle) and then arbitrarily move it one
direction (to find a group boundary). The original split point is the most
optimal, in terms of splitting. Thus, we should find the nearest usable split
point to that row and maintain as optimal a split as possible.
Sure in the example I gave it is an extreme case, but even ignoring that you
might end up with non-optimal splits. It may be the case that moving down 1
single row would find a group boundary, yet we move up back rows anyway.
> Add DelimitedKeyPrefixRegionSplitPolicy
> ---------------------------------------
>
> Key: HBASE-7748
> URL: https://issues.apache.org/jira/browse/HBASE-7748
> Project: HBase
> Issue Type: New Feature
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Fix For: 0.96.0, 0.94.5
>
> Attachments: hbase-7748_v1.patch, hbase-7748_v2.patch,
> hbase-7748_v3-0.94.patch, hbase-7748_v3.patch
>
>
> DelimitedKeyPrefixRegionSplitPolicy similar to KeyPrefixRegionSplitPolicy,
> but with a delimiter for the key, instead of a fixed prefix.
> Can be used for META regions, since we are doing
> table_name,start_key,region_id.encoded_region_name.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
