[jira] [Commented] (PHOENIX-6844) Provide multiple IndexRegionSplitPolicy implementations

["Istvan Toth (Jira)" <ji...@apache.org>]

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

Istvan Toth commented on PHOENIX-6844:
--------------------------------------

Tuning the global _hbase.increasing.policy.initial.size_ property is the best alternative currently.

> Provide multiple IndexRegionSplitPolicy implementations
> -------------------------------------------------------
>
>                 Key: PHOENIX-6844
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6844
>             Project: Phoenix
>          Issue Type: Wish
>          Components: core
>            Reporter: Istvan Toth
>            Priority: Major
>              Labels: beginner
>
> We currently inherit IndexRegionSplitPolicy from SteppingSplitPolicy, which is the modern HBase default, and provides a good balance between parallelization and conserving the number of regions.
> However, users may want to use more or less parallelization for specific tables.
> Providing IndexRegionSplitPolicy variants extending IncreasingToUpperBoundRegionSplitPolicy and ConstantSizeRegionSplitPolicy would enable better tuning of split behaviour for tables with local indexes.
> We should also add a property to specify the default SplitPolicy for when adding a local index for the first time.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)