[jira] [Commented] (HBASE-20530) Composition of backup directory containing namespace when restoring is different from the actual hfile location
[ https://issues.apache.org/jira/browse/HBASE-20530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16478982#comment-16478982 ] Hudson commented on HBASE-20530: Results for branch master [build #334 on builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/334/]: (x) *{color:red}-1 overall{color}* details (if available): (/) {color:green}+1 general checks{color} -- For more information [see general report|https://builds.apache.org/job/HBase%20Nightly/job/master/334//General_Nightly_Build_Report/] (x) {color:red}-1 jdk8 hadoop2 checks{color} -- For more information [see jdk8 (hadoop2) report|https://builds.apache.org/job/HBase%20Nightly/job/master/334//JDK8_Nightly_Build_Report_(Hadoop2)/] (x) {color:red}-1 jdk8 hadoop3 checks{color} -- For more information [see jdk8 (hadoop3) report|https://builds.apache.org/job/HBase%20Nightly/job/master/334//JDK8_Nightly_Build_Report_(Hadoop3)/] (/) {color:green}+1 source release artifact{color} -- See build output for details. > 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 > Fix For: 3.0.0 > > Attachments: 20530-v3.patch, 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)
[jira] [Commented] (HBASE-20530) Composition of backup directory containing namespace when restoring is different from the actual hfile location
[ https://issues.apache.org/jira/browse/HBASE-20530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477966#comment-16477966 ] Hadoop QA commented on HBASE-20530: --- | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 14s{color} | {color:blue} Docker mode activated. {color} | || || || || {color:brown} Prechecks {color} || | {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m 0s{color} | {color:green} Patch does not have any anti-patterns. {color} | | {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s{color} | {color:green} The patch does not contain any @author tags. {color} | | {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m 0s{color} | {color:green} The patch appears to include 3 new or modified test files. {color} | || || || || {color:brown} master Compile Tests {color} || | {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 10s{color} | {color:blue} Maven dependency ordering for branch {color} | | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m 5s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 47s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 25s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m 4s{color} | {color:green} branch has no errors when building our shaded downstream artifacts. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m 58s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 22s{color} | {color:green} master passed {color} | || || || || {color:brown} Patch Compile Tests {color} || | {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 12s{color} | {color:blue} Maven dependency ordering for patch {color} | | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m 10s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 48s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 48s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 24s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m 0s{color} | {color:green} The patch has no whitespace issues. {color} | | {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m 8s{color} | {color:green} patch has no errors when building our shaded downstream artifacts. {color} | | {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 12m 52s{color} | {color:green} Patch does not cause any errors with Hadoop 2.6.5 2.7.4 or 3.0.0. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m 15s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 24s{color} | {color:green} the patch passed {color} | || || || || {color:brown} Other Tests {color} || | {color:green}+1{color} | {color:green} unit {color} | {color:green} 12m 36s{color} | {color:green} hbase-mapreduce in the patch passed. {color} | | {color:green}+1{color} | {color:green} unit {color} | {color:green} 13m 6s{color} | {color:green} hbase-backup in the patch passed. {color} | | {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m 20s{color} | {color:green} The patch does not generate ASF License warnings. {color} | | {color:black}{color} | {color:black} {color} | {color:black} 61m 53s{color} | {color:black} {color} | \\ \\ || Subsystem || Report/Notes || | Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:d8b550f | | JIRA Issue | HBASE-20530 | | JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12923743/20530-v3.patch | | Optional Tests | asflicense javac javadoc unit findbugs shadedjars hadoopcheck hbaseanti checkstyle compile | | uname | Linux 288efc732c5e 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12 13:48:03 UTC 2016 x86_64 GNU/Linux | | Build tool | maven | | Personality | /home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build@2/component/dev-support/hbase-personality.sh | | git revision | master / 2c32272dfa | | maven | version: Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T19:49:05Z) | | Default Java | 1.8.0_171 | | fin
[jira] [Commented] (HBASE-20530) Composition of backup directory containing namespace when restoring is different from the actual hfile location
[ https://issues.apache.org/jira/browse/HBASE-20530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16476618#comment-16476618 ] Ted Yu commented on HBASE-20530: Tests are currently broken in master branch. Stay tuned for failing tests to be fixed. > 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)
[jira] [Commented] (HBASE-20530) Composition of backup directory containing namespace when restoring is different from the actual hfile location
[ https://issues.apache.org/jira/browse/HBASE-20530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16476614#comment-16476614 ] Vladimir Rodionov commented on HBASE-20530: --- Are we good to go now, [~yuzhih...@gmail.com]? > 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)
[jira] [Commented] (HBASE-20530) Composition of backup directory containing namespace when restoring is different from the actual hfile location
[ https://issues.apache.org/jira/browse/HBASE-20530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16476457#comment-16476457 ] Hadoop QA commented on HBASE-20530: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 3m 19s{color} | {color:blue} Docker mode activated. {color} | || || || || {color:brown} Prechecks {color} || | {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m 0s{color} | {color:green} Patch does not have any anti-patterns. {color} | | {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s{color} | {color:green} The patch does not contain any @author tags. {color} | | {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m 0s{color} | {color:green} The patch appears to include 3 new or modified test files. {color} | || || || || {color:brown} master Compile Tests {color} || | {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 27s{color} | {color:blue} Maven dependency ordering for branch {color} | | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m 59s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 1s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 34s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 5m 5s{color} | {color:green} branch has no errors when building our shaded downstream artifacts. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m 22s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 31s{color} | {color:green} master passed {color} | || || || || {color:brown} Patch Compile Tests {color} || | {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 13s{color} | {color:blue} Maven dependency ordering for patch {color} | | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m 6s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 2s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m 2s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 31s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m 0s{color} | {color:green} The patch has no whitespace issues. {color} | | {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m 55s{color} | {color:green} patch has no errors when building our shaded downstream artifacts. {color} | | {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 16m 13s{color} | {color:green} Patch does not cause any errors with Hadoop 2.6.5 2.7.4 or 3.0.0. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m 41s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 32s{color} | {color:green} the patch passed {color} | || || || || {color:brown} Other Tests {color} || | {color:red}-1{color} | {color:red} unit {color} | {color:red} 19m 51s{color} | {color:red} hbase-mapreduce in the patch failed. {color} | | {color:green}+1{color} | {color:green} unit {color} | {color:green} 15m 21s{color} | {color:green} hbase-backup in the patch passed. {color} | | {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m 25s{color} | {color:green} The patch does not generate ASF License warnings. {color} | | {color:black}{color} | {color:black} {color} | {color:black} 83m 51s{color} | {color:black} {color} | \\ \\ || Reason || Tests || | Failed junit tests | hadoop.hbase.mapreduce.TestHashTable | | | hadoop.hbase.mapreduce.TestSyncTable | \\ \\ || Subsystem || Report/Notes || | Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:d8b550f | | JIRA Issue | HBASE-20530 | | JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12923540/HBASE-20530-v3.patch | | Optional Tests | asflicense javac javadoc unit findbugs shadedjars hadoopcheck hbaseanti checkstyle compile | | uname | Linux 4f4d40074db6 3.13.0-137-generic #186-Ubuntu SMP Mon Dec 4 19:09:19 UTC 2017 x86_64 GNU/Linux | | Build tool | maven | | Personality | /home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh | | git revision | master / 26babcf013 | | maven |
[jira] [Commented] (HBASE-20530) Composition of backup directory containing namespace when restoring is different from the actual hfile location
[ https://issues.apache.org/jira/browse/HBASE-20530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16474870#comment-16474870 ] Vladimir Rodionov commented on HBASE-20530: --- OK, go ahead. > 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)
[jira] [Commented] (HBASE-20530) Composition of backup directory containing namespace when restoring is different from the actual hfile location
[ https://issues.apache.org/jira/browse/HBASE-20530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16474855#comment-16474855 ] Ted Yu commented on HBASE-20530: It would be better to get a clean QA run first. > 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)
[jira] [Commented] (HBASE-20530) Composition of backup directory containing namespace when restoring is different from the actual hfile location
[ https://issues.apache.org/jira/browse/HBASE-20530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16474845#comment-16474845 ] Vladimir Rodionov commented on HBASE-20530: --- Test failures are not related to the patch. Confirmed running all suite locally. > 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)
[jira] [Commented] (HBASE-20530) Composition of backup directory containing namespace when restoring is different from the actual hfile location
[ https://issues.apache.org/jira/browse/HBASE-20530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16473578#comment-16473578 ] Ted Yu commented on HBASE-20530: Release note is needed to document the change in output directory structure when writeMultipleTables is true. > 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)
[jira] [Commented] (HBASE-20530) Composition of backup directory containing namespace when restoring is different from the actual hfile location
[ https://issues.apache.org/jira/browse/HBASE-20530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471226#comment-16471226 ] Hadoop QA commented on HBASE-20530: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 12s{color} | {color:blue} Docker mode activated. {color} | || || || || {color:brown} Prechecks {color} || | {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m 0s{color} | {color:green} Patch does not have any anti-patterns. {color} | | {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s{color} | {color:green} The patch does not contain any @author tags. {color} | | {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m 0s{color} | {color:green} The patch appears to include 3 new or modified test files. {color} | || || || || {color:brown} master Compile Tests {color} || | {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 12s{color} | {color:blue} Maven dependency ordering for branch {color} | | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m 48s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 57s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 26s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m 34s{color} | {color:green} branch has no errors when building our shaded downstream artifacts. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m 15s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 31s{color} | {color:green} master passed {color} | || || || || {color:brown} Patch Compile Tests {color} || | {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 13s{color} | {color:blue} Maven dependency ordering for patch {color} | | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m 0s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 57s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 57s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 32s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m 0s{color} | {color:green} The patch has no whitespace issues. {color} | | {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m 55s{color} | {color:green} patch has no errors when building our shaded downstream artifacts. {color} | | {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 15m 58s{color} | {color:green} Patch does not cause any errors with Hadoop 2.6.5 2.7.4 or 3.0.0. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m 39s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 30s{color} | {color:green} the patch passed {color} | || || || || {color:brown} Other Tests {color} || | {color:green}+1{color} | {color:green} unit {color} | {color:green} 12m 31s{color} | {color:green} hbase-mapreduce in the patch passed. {color} | | {color:red}-1{color} | {color:red} unit {color} | {color:red} 22m 12s{color} | {color:red} hbase-backup in the patch failed. {color} | | {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m 27s{color} | {color:green} The patch does not generate ASF License warnings. {color} | | {color:black}{color} | {color:black} {color} | {color:black} 78m 32s{color} | {color:black} {color} | \\ \\ || Reason || Tests || | Failed junit tests | hadoop.hbase.backup.TestBackupDescribe | | | hadoop.hbase.backup.TestIncrementalBackupMergeWithFailures | | | hadoop.hbase.backup.TestIncrementalBackupWithBulkLoad | | | hadoop.hbase.backup.TestIncrementalBackupWithFailures | \\ \\ || Subsystem || Report/Notes || | Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:d8b550f | | JIRA Issue | HBASE-20530 | | JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12922908/HBASE-20530-v3.patch | | Optional Tests | asflicense javac javadoc unit findbugs shadedjars hadoopcheck hbaseanti checkstyle compile | | uname | Linux 139e267aa55f 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12 13:48:03 UTC 2016 x86_64 GNU/Linux | | Build tool | maven | | Personality | /home/je
[jira] [Commented] (HBASE-20530) Composition of backup directory containing namespace when restoring is different from the actual hfile location
[ https://issues.apache.org/jira/browse/HBASE-20530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471090#comment-16471090 ] Vladimir Rodionov commented on HBASE-20530: --- Patch v3. Fixes javac and checkstyle warnings > 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)
[jira] [Commented] (HBASE-20530) Composition of backup directory containing namespace when restoring is different from the actual hfile location
[ https://issues.apache.org/jira/browse/HBASE-20530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16469868#comment-16469868 ] Ted Yu commented on HBASE-20530: Vlad: Please fix the javac and checkstyle warnings. > 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 > > > 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)
[jira] [Commented] (HBASE-20530) Composition of backup directory containing namespace when restoring is different from the actual hfile location
[ https://issues.apache.org/jira/browse/HBASE-20530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16469860#comment-16469860 ] Hadoop QA commented on HBASE-20530: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 14s{color} | {color:blue} Docker mode activated. {color} | || || || || {color:brown} Prechecks {color} || | {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m 0s{color} | {color:green} Patch does not have any anti-patterns. {color} | | {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s{color} | {color:green} The patch does not contain any @author tags. {color} | | {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m 0s{color} | {color:green} The patch appears to include 3 new or modified test files. {color} | || || || || {color:brown} master Compile Tests {color} || | {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 25s{color} | {color:blue} Maven dependency ordering for branch {color} | | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m 34s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 52s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 30s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m 19s{color} | {color:green} branch has no errors when building our shaded downstream artifacts. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m 4s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 27s{color} | {color:green} master passed {color} | || || || || {color:brown} Patch Compile Tests {color} || | {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 14s{color} | {color:blue} Maven dependency ordering for patch {color} | | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m 12s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 52s{color} | {color:green} the patch passed {color} | | {color:red}-1{color} | {color:red} javac {color} | {color:red} 0m 28s{color} | {color:red} hbase-mapreduce generated 1 new + 159 unchanged - 0 fixed = 160 total (was 159) {color} | | {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 0m 17s{color} | {color:red} hbase-mapreduce: The patch generated 1 new + 56 unchanged - 0 fixed = 57 total (was 56) {color} | | {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m 0s{color} | {color:green} The patch has no whitespace issues. {color} | | {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m 17s{color} | {color:green} patch has no errors when building our shaded downstream artifacts. {color} | | {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 13m 5s{color} | {color:green} Patch does not cause any errors with Hadoop 2.6.5 2.7.4 or 3.0.0. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m 18s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 27s{color} | {color:green} the patch passed {color} | || || || || {color:brown} Other Tests {color} || | {color:green}+1{color} | {color:green} unit {color} | {color:green} 12m 26s{color} | {color:green} hbase-mapreduce in the patch passed. {color} | | {color:green}+1{color} | {color:green} unit {color} | {color:green} 11m 52s{color} | {color:green} hbase-backup in the patch passed. {color} | | {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m 18s{color} | {color:green} The patch does not generate ASF License warnings. {color} | | {color:black}{color} | {color:black} {color} | {color:black} 62m 35s{color} | {color:black} {color} | \\ \\ || Subsystem || Report/Notes || | Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:d8b550f | | JIRA Issue | HBASE-20530 | | JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12922769/HBASE-20530-v2.patch | | Optional Tests | asflicense javac javadoc unit findbugs shadedjars hadoopcheck hbaseanti checkstyle compile | | uname | Linux 916d0f20175f 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12 13:48:03 UTC 2016 x86_64 GNU/Linux | | Build tool | maven | | Personality | /home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh | | git revision | master / 9c046c091c | | maven | version:
[jira] [Commented] (HBASE-20530) Composition of backup directory containing namespace when restoring is different from the actual hfile location
[ https://issues.apache.org/jira/browse/HBASE-20530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16469832#comment-16469832 ] Ted Yu commented on HBASE-20530: [~denselm]: Can you take a look at the patch (since the multi table feature was your work) ? Thanks > 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 > > > 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)
[jira] [Commented] (HBASE-20530) Composition of backup directory containing namespace when restoring is different from the actual hfile location
[ https://issues.apache.org/jira/browse/HBASE-20530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16469828#comment-16469828 ] Vladimir Rodionov commented on HBASE-20530: --- To preserve old behavior. B&R always run in writeMultipleTables=true mode > 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 > > > 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)
[jira] [Commented] (HBASE-20530) Composition of backup directory containing namespace when restoring is different from the actual hfile location
[ https://issues.apache.org/jira/browse/HBASE-20530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16469820#comment-16469820 ] Ted Yu commented on HBASE-20530: {code} + String tn = writeMultipleTables? + tableInfo.getRegionLocator().getName().getNameWithNamespaceInclAsString(): {code} Why the namespace would not be included when writeMultipleTables is false ? > 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 > > > 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)
[jira] [Commented] (HBASE-20530) Composition of backup directory containing namespace when restoring is different from the actual hfile location
[ https://issues.apache.org/jira/browse/HBASE-20530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16469798#comment-16469798 ] Vladimir Rodionov commented on HBASE-20530: --- Patch v2 takes care of failed UTs > 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 > > > 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)
[jira] [Commented] (HBASE-20530) Composition of backup directory containing namespace when restoring is different from the actual hfile location
[ https://issues.apache.org/jira/browse/HBASE-20530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16469461#comment-16469461 ] Hadoop QA commented on HBASE-20530: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 2m 49s{color} | {color:blue} Docker mode activated. {color} | || || || || {color:brown} Prechecks {color} || | {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m 0s{color} | {color:green} Patch does not have any anti-patterns. {color} | | {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s{color} | {color:green} The patch does not contain any @author tags. {color} | | {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m 0s{color} | {color:green} The patch appears to include 2 new or modified test files. {color} | || || || || {color:brown} master Compile Tests {color} || | {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 1m 18s{color} | {color:blue} Maven dependency ordering for branch {color} | | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 6m 24s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 56s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 29s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m 16s{color} | {color:green} branch has no errors when building our shaded downstream artifacts. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m 2s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 33s{color} | {color:green} master passed {color} | || || || || {color:brown} Patch Compile Tests {color} || | {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 15s{color} | {color:blue} Maven dependency ordering for patch {color} | | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m 10s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 50s{color} | {color:green} the patch passed {color} | | {color:red}-1{color} | {color:red} javac {color} | {color:red} 0m 27s{color} | {color:red} hbase-mapreduce generated 1 new + 159 unchanged - 0 fixed = 160 total (was 159) {color} | | {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 0m 16s{color} | {color:red} hbase-mapreduce: The patch generated 2 new + 18 unchanged - 0 fixed = 20 total (was 18) {color} | | {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m 0s{color} | {color:green} The patch has no whitespace issues. {color} | | {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m 17s{color} | {color:green} patch has no errors when building our shaded downstream artifacts. {color} | | {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 13m 7s{color} | {color:green} Patch does not cause any errors with Hadoop 2.6.5 2.7.4 or 3.0.0. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m 18s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 26s{color} | {color:green} the patch passed {color} | || || || || {color:brown} Other Tests {color} || | {color:red}-1{color} | {color:red} unit {color} | {color:red} 19m 51s{color} | {color:red} hbase-mapreduce in the patch failed. {color} | | {color:green}+1{color} | {color:green} unit {color} | {color:green} 11m 44s{color} | {color:green} hbase-backup in the patch passed. {color} | | {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m 22s{color} | {color:green} The patch does not generate ASF License warnings. {color} | | {color:black}{color} | {color:black} {color} | {color:black} 75m 13s{color} | {color:black} {color} | \\ \\ || Reason || Tests || | Failed junit tests | hadoop.hbase.snapshot.TestMobSecureExportSnapshot | | | hadoop.hbase.snapshot.TestSecureExportSnapshot | | | hadoop.hbase.snapshot.TestMobExportSnapshot | | | hadoop.hbase.mapreduce.TestHFileOutputFormat2 | | | hadoop.hbase.snapshot.TestExportSnapshot | \\ \\ || Subsystem || Report/Notes || | Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:d8b550f | | JIRA Issue | HBASE-20530 | | JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12922706/HBASE-20530-v1.patch | | Optional Tests | asflicense javac javadoc unit findbugs shadedjars hadoopcheck hbaseanti checkstyle compile | | uname
[jira] [Commented] (HBASE-20530) Composition of backup directory containing namespace when restoring is different from the actual hfile location
[ https://issues.apache.org/jira/browse/HBASE-20530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16469349#comment-16469349 ] Vladimir Rodionov commented on HBASE-20530: --- Hey, [~maxwellguo]. Could you please next time to open Apache JIRA when you find a bug? This will helps community a lot. > 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 > > > 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)
[jira] [Commented] (HBASE-20530) Composition of backup directory containing namespace when restoring is different from the actual hfile location
[ https://issues.apache.org/jira/browse/HBASE-20530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16468509#comment-16468509 ] maxwellguo commented on HBASE-20530: I also meet this question ,and i have fixed this bug on my own code ,also i do some tests of backup and restore on hdfs and other fs. it looks like good. I just change the copy dest path of hfile (covered from wal ). after write some unit test ,i will attached the path latter. > 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)
[jira] [Commented] (HBASE-20530) Composition of backup directory containing namespace when restoring is different from the actual hfile location
[ 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)