[
https://issues.apache.org/jira/browse/HADOOP-730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567408#action_12567408
]
Hadoop QA commented on HADOOP-730:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12375163/730-0.patch
against trunk revision 619744.
@author +1. The patch does not contain any @author tags.
tests included -1. The patch doesn't appear to include any new or modified
tests.
Please justify why no tests are needed for this patch.
javadoc +1. The javadoc tool did not generate any warning messages.
javac -1. The applied patch generated 614 javac compiler warnings (more
than the trunk's current 612 warnings).
release audit +1. The applied patch does not generate any new release
audit warnings.
findbugs +1. The patch does not introduce any new Findbugs warnings.
core tests -1. The patch failed core unit tests.
contrib tests +1. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1767/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1767/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1767/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1767/console
This message is automatically generated.
> Local file system uses copy to implement rename
> -----------------------------------------------
>
> Key: HADOOP-730
> URL: https://issues.apache.org/jira/browse/HADOOP-730
> Project: Hadoop Core
> Issue Type: Bug
> Components: fs
> Affects Versions: 0.8.0
> Reporter: Owen O'Malley
> Assignee: Chris Douglas
> Fix For: 0.16.1
>
> Attachments: 730-0.patch
>
>
> There is a variable LocalFileSystem.useCopyForRename that is set to true.
> When true, the local file system will implement rename as a copy followed by
> a delete. This is likely a performance problem. Is there a reason that
> useCopyForRename is set?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
