Hudson commented on HBASE-20859:

Results for branch master
        [build #394 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/394/]: (x) 
*{color:red}-1 overall{color}*
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 

(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 

(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 

(/) {color:green}+1 source release artifact{color}
-- See build output for details.

(/) {color:green}+1 client integration test{color}

> Backup and incremental load could fail in secure clusters
> ---------------------------------------------------------
>                 Key: HBASE-20859
>                 URL: https://issues.apache.org/jira/browse/HBASE-20859
>             Project: HBase
>          Issue Type: Bug
>          Components: backup&restore
>            Reporter: Wei-Chiu Chuang
>            Assignee: Wei-Chiu Chuang
>            Priority: Major
>             Fix For: 3.0.0
>         Attachments: HBASE-20859.master.001.patch, 
> HBASE-20859.master.002.patch, HBASE-20859.master.003.patch
> HBase Backup and incremental load uses 
> HConstants.DEFAULT_TEMPORARY_HDFS_DIRECTORY for temporary path.
> HConstants.DEFAULT_TEMPORARY_HDFS_DIRECTORY uses the Java runtime user name 
> to generate a temporary path on HDFS. This can be a wrong assumption in a 
> secure cluster where Kerberos principal name can be different from the system 
> user name.
> {code:java}
> public static final String DEFAULT_TEMPORARY_HDFS_DIRECTORY = "/user/"
>       + System.getProperty("user.name") + "/hbase-staging";
> {code}
> This constant variable is used in BackupUtils.java and HFileOutputFormat2.java
> In such cases, you will not be able to write files to the temporary location 
> on HDFS due to permission error, and therefore operations such as backup will 
> fail.
> This bug is similar in nature to HDFS-12485.

This message was sent by Atlassian JIRA

Reply via email to