[
https://issues.apache.org/jira/browse/HBASE-20530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16464531#comment-16464531
]
Ted Yu commented on HBASE-20530:
--------------------------------
MultiTableHFileOutputFormat.configureIncrementalLoad has this code:
{code}
allTableNames.add(tableInfo.getRegionLocator().getName().getNameAsString());
{code}
>From TableName:
{code}
// The name does not include the namespace when it's the default one.
this.nameAsString = qualifierAsString;
{code}
I think this is why the namespace was missing in the path.
HBackupFileSystem.getTableBackupDir can use similar logic to accommodate the
above.
> Composition of backup directory containing namespace when restoring is
> different from the actual hfile location
> ---------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-20530
> URL: https://issues.apache.org/jira/browse/HBASE-20530
> Project: HBase
> Issue Type: Bug
> Reporter: Ted Yu
> Assignee: Vladimir Rodionov
> Priority: Critical
>
> Here is partial listing of output from incremental backup:
> {code}
> 5306 2018-05-04 02:38
> hdfs://mycluster/user/hbase/backup_loc/backup_1525401467793/table_almphxih4u/cf1/5648501da7194783947bbf07b172f07e
> {code}
> When restoring, here is what HBackupFileSystem.getTableBackupDir returns:
> {code}
> fileBackupDir=hdfs://mycluster/user/hbase/backup_loc/backup_1525401467793/default/table_almphxih4u
> {code}
> You can see that namespace gets in the way, leading to inability of finding
> the proper hfile.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
