[
https://issues.apache.org/jira/browse/HBASE-20530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Rodionov updated HBASE-20530:
--------------------------------------
Release Note: There is a directory layout change (tables with default
namespace now get additional level in directory structure of the WALPlayer
output) for WALPlayer output in WAL - to- HFile conversion mode, but only when
multiple tables are specified (this is case only for backup module). The other
tools using WALPLayer are not affected (unless they use multiple tables mode
introduced by B&R feature). (was: There is a directory layout change (tables
with default namespace now get additional level in directory structure of the
WALPlayer output) for WALPlayer output in WAL - to- HFile conversion mode, but
only when multiple tables are specified (this is case only for backup module).
The other tools using WALPLayer are not affected.)
> 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
> Attachments: HBASE-20530-v1.patch, HBASE-20530-v2.patch,
> HBASE-20530-v3.patch
>
>
> 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)
