hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (Jira)" <j...@apache.org>
Subject [jira] [Work logged] (HADOOP-16878) FileUtil.copy() to throw IOException if the source and destination are the same
Date Fri, 16 Oct 2020 20:05:00 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-16878?focusedWorklogId=501665&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-501665

ASF GitHub Bot logged work on HADOOP-16878:

                Author: ASF GitHub Bot
            Created on: 16/Oct/20 20:04
            Start Date: 16/Oct/20 20:04
    Worklog Time Spent: 10m 
      Work Description: ayushtkn merged pull request #2383:
URL: https://github.com/apache/hadoop/pull/2383


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:

Issue Time Tracking

    Worklog Id:     (was: 501665)
    Time Spent: 2h 10m  (was: 2h)

> FileUtil.copy() to throw IOException if the source and destination are the same
> -------------------------------------------------------------------------------
>                 Key: HADOOP-16878
>                 URL: https://issues.apache.org/jira/browse/HADOOP-16878
>             Project: Hadoop Common
>          Issue Type: Improvement
>    Affects Versions: 3.3.0
>            Reporter: Gabor Bota
>            Assignee: Gabor Bota
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.4.0
>         Attachments: hdfsTest.patch
>          Time Spent: 2h 10m
>  Remaining Estimate: 0h
> We encountered an error during a test in our QE when the file destination and source
path were the same. This happened during an ADLS test, and there were no meaningful error
messages, so it was hard to find the root cause of the failure.
> The error we saw was that file size has changed during the copy operation. The new file
creation in the destination - which is the same as the source - creates a file and sets the
file length to zero. After this, getting the source file will fail because the sile size changed
during the operation.
> I propose a solution to at least log in error level in the {{FileUtil}} if the source
and destination of the copy operation is the same, so debugging issues like this will be easier
in the future.

This message was sent by Atlassian Jira

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message