[
https://issues.apache.org/jira/browse/HBASE-20111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16415405#comment-16415405
]
Rajeshbabu Chintaguntla commented on HBASE-20111:
-------------------------------------------------
bq.Don't you want this to be: !(info.isMetaRegion() ||
TableName.NAMESPACE_TABLE_NAME.equals(info.getTable()))? The part of the
conditional will never be true because isMetaRegion is only true for the
hbase:meta table.
Yes [~elserj] it's my blunder. Now in the patch just checking for meta only to
not split anytime. [~stack] can you confirm whether we can allow splitting
namespace or not as Josh mentioned in the above comment. If it's ok to split
the namespace then I can commit this patch.
> Able to split region explicitly even on shouldSplit return false from split
> policy
> ----------------------------------------------------------------------------------
>
> Key: HBASE-20111
> URL: https://issues.apache.org/jira/browse/HBASE-20111
> Project: HBase
> Issue Type: Bug
> Reporter: Rajeshbabu Chintaguntla
> Assignee: Rajeshbabu Chintaguntla
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: HBASE-20111.001.branch-2.0.patch, HBASE-20111.patch,
> HBASE-20111_test.patch, HBASE-20111_v2.patch, HBASE-20111_v3.patch
>
>
> Currently able to split the region explicitly even when the split policy
> returns from shouldSplit.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
