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

Hudson commented on MAPREDUCE-4549:
-----------------------------------

Integrated in Hadoop-Hdfs-0.23-Build #347 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/347/])
    MAPREDUCE-4549. Distributed cache conflicts breaks backwards compatability 
(Robert Evans via tgraves) (Revision 1374407)

     Result = SUCCESS
tgraves : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1374407
Files : 
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
* 
/hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapreduce/v2/util/MRApps.java
* 
/hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/test/java/org/apache/hadoop/mapreduce/v2/util/TestMRApps.java

                
> 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
>             Fix For: 0.23.3
>
>         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

        

Reply via email to