Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Sat, 18 Aug 2012 06:25:38 +1100 (NCT)
From: "Robert Joseph Evans (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <1547783774.24890.1345231538414.JavaMail.jiratomcat@arcas>
In-Reply-To: <1504610550.1886.1344868238150.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (MAPREDUCE-4549) Distributed cache conflicts
 breaks backwards compatability
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/MAPREDUCE-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436993#comment-13436993 ] 

Robert Joseph Evans commented on MAPREDUCE-4549:
------------------------------------------------

That is fine with me. I realize that a lot of people are not going to use 0.23 as a bridge between 1.0 and 2.0 so if we want it to be deprecated in 2.0 too that is fine.  If we revert MAPREDUCE-4503 this patch should apply cleanly to branch-2 also.
                
> Distributed cache conflicts breaks backwards compatability
> ----------------------------------------------------------
>
>                 Key: MAPREDUCE-4549
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4549
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.3
>            Reporter: Robert Joseph Evans
>            Assignee: Robert Joseph Evans
>            Priority: Critical
>         Attachments: MR-4549-branch-0.23.txt
>
>
> I recently put in MAPREDUCE-4503 which went a bit too far, and broke backwards compatibility with 1.0 in distribtued cache entries.  instead of changing the behavior of the distributed cache to more closely match 1.0 behavior I want to just change the exception to a warning message informing the users that it will become an error in 2.0

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira