[
https://issues.apache.org/jira/browse/HDFS-8036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389855#comment-14389855
]
Hadoop QA commented on HDFS-8036:
---------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12708575/HDFS-8036.000.patch
against trunk revision 2daa478.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-tools/hadoop-distcp.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/10136//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HDFS-Build/10136//console
This message is automatically generated.
> Use snapshot path as source when using snapshot diff report in DistCp
> ---------------------------------------------------------------------
>
> Key: HDFS-8036
> URL: https://issues.apache.org/jira/browse/HDFS-8036
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: distcp
> Affects Versions: 2.7.0
> Reporter: Jing Zhao
> Assignee: Jing Zhao
> Attachments: HDFS-8036.000.patch
>
>
> When using snapshot diff report for distcp (HDFS-7535), the semantic should
> be apply the diff to the target in order to sync the target with
> source@snapshot2. Therefore after syncing based on the snapshot diff report,
> we should append the name of snapshot2 to the original source path and use it
> as the new source name.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
