[
https://issues.apache.org/jira/browse/HBASE-18773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157904#comment-16157904
]
Zach York commented on HBASE-18773:
-----------------------------------
For some reason RB is not letting me publish my comment. Putting it here for
now:
[~uagashe], yes the HRegionInfo methods used this new method I created in the
implementation (in a separate patch).
[~stack], do you mean something like what I have below (dynamic isMeta):
public boolean isMeta() {
String[] parts =
getNameWithNamespaceInclAsString().split(String.valueOf(NAMESPACE_DELIM));
if (parts[0].equals(NamespaceDescriptor.SYSTEM_NAMESPACE_NAME_STR) &&
parts[1].contains(DEFAULT_META_TABLE_NAME_STR)) {
return true;
}
return false;
}
The only issue I see with this approach is that it might be confusing for
TableName.isMetaTableName() and tableName.isMeta to return different results.
> Add utility to determine if a TableName is a meta table
> -------------------------------------------------------
>
> Key: HBASE-18773
> URL: https://issues.apache.org/jira/browse/HBASE-18773
> Project: HBase
> Issue Type: Sub-task
> Reporter: Zach York
> Assignee: Zach York
> Attachments: HBASE-18773.HBASE-18477.001.patch
>
>
> HBASE-18444 adds a method of specifying a meta table suffix. To continue work
> on HBASE-18477, we need a way to determine if a TableName is a meta table.
> This patch adds this method and a unit test.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
