You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Anoop Sam John (Jira)" <ji...@apache.org> on 2020/06/01 03:59:00 UTC

[jira] [Commented] (HBASE-24472) Enhanced version of KeyPrefixRegionSplitPolicy

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

Anoop Sam John commented on HBASE-24472:
----------------------------------------

It make sense.  You might not need new Split policy. To existing policy DelimitedKeyPrefixRegionSplitPolicy can add n optional param regarding the ordinal of the delimiter (Default is 1 anyways)

> Enhanced version of KeyPrefixRegionSplitPolicy
> ----------------------------------------------
>
>                 Key: HBASE-24472
>                 URL: https://issues.apache.org/jira/browse/HBASE-24472
>             Project: HBase
>          Issue Type: Improvement
>          Components: regionserver
>            Reporter: Anil Sadineni
>            Priority: Major
>
> With KeyPrefixRegionSplitPolicy and DelimitedKeyPrefixRegionSplitPolicy, splitting regions policy is limited to either fixed length or based on delimiter. With Yarn Application Timeline Server V2, as discussed in YARN-10077, it will be nice to have enhanced version of DelimitedKeyPrefixRegionSplitPolicy that will give more flexibility to users to define the ordinance of delimiter to consider.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)