You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Chris Douglas (JIRA)" <ji...@apache.org> on 2008/03/20 22:25:24 UTC

[jira] Resolved: (HADOOP-3059) 0.16.1 breaks backwards API compatibility with fix for HADOOP-2808

     [ https://issues.apache.org/jira/browse/HADOOP-3059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Douglas resolved HADOOP-3059.
-----------------------------------

    Resolution: Won't Fix

HADOOP-2808 didn't introduce a new signature for copy; it enforced the existing one. As indicated in the JIRA, setting the "overwrite" parameter had no effect on the copy. This isn't an API change; the overwrite formal was added to a private, static function. The former behavior can be restored by setting overwrite to false.

> 0.16.1 breaks backwards API compatibility with fix for HADOOP-2808
> ------------------------------------------------------------------
>
>                 Key: HADOOP-3059
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3059
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.16.1
>            Reporter: Subramaniam Krishnan
>             Fix For: 0.16.2
>
>
> HADOOP-2808 introduced a new signature for the copy method that takes an overwrite flag. 
> Before this patch the behavior, for the pre-existing copy method, was that if the destination existed an IOException was thrown. After this patch the behavior, for the pre-existing copy method, is that if the destination exists it is overwritten.
> The behavior of the pre-existing copy method should not have changed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.