[jira] [Commented] (MAPREDUCE-4549) Distributed cache conflicts breaks backwards compatability
[ https://issues.apache.org/jira/browse/MAPREDUCE-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13614367#comment-13614367 ] Roman Shaposhnik commented on MAPREDUCE-4549: - All the findings are attached over here: MAPREDUCE-4820 At this point I'd agree with Arun and close this one. We can track what's left over at MAPREDUCE-4820 > 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, 2.0.2-alpha >Reporter: Robert Joseph Evans >Assignee: Robert Joseph Evans >Priority: Blocker > Fix For: 0.23.5, 2.0.4-alpha > > Attachments: MAPREDUCE-4549-trunk.patch, 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 For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4549) Distributed cache conflicts breaks backwards compatability
[ https://issues.apache.org/jira/browse/MAPREDUCE-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13614340#comment-13614340 ] Arun C Murthy commented on MAPREDUCE-4549: -- Ok, that is news to me. Can we please close this and open a new jira then? Tx. > 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, 2.0.2-alpha >Reporter: Robert Joseph Evans >Assignee: Robert Joseph Evans >Priority: Blocker > Fix For: 0.23.5, 2.0.4-alpha > > Attachments: MAPREDUCE-4549-trunk.patch, 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 For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4549) Distributed cache conflicts breaks backwards compatability
[ https://issues.apache.org/jira/browse/MAPREDUCE-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13613413#comment-13613413 ] Alejandro Abdelnur commented on MAPREDUCE-4549: --- I think the problem is different, Roman would you please post the findings you send me. Thx > 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, 2.0.2-alpha >Reporter: Robert Joseph Evans >Assignee: Robert Joseph Evans >Priority: Blocker > Fix For: 0.23.5, 2.0.4-alpha > > Attachments: MAPREDUCE-4549-trunk.patch, 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 For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4549) Distributed cache conflicts breaks backwards compatability
[ https://issues.apache.org/jira/browse/MAPREDUCE-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13612915#comment-13612915 ] Arun C Murthy commented on MAPREDUCE-4549: -- Also, verified that the same fix is present in branch-2.0.4-alpha. > 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, 2.0.2-alpha >Reporter: Robert Joseph Evans >Assignee: Robert Joseph Evans >Priority: Blocker > Fix For: 0.23.5, 2.0.4-alpha > > Attachments: MAPREDUCE-4549-trunk.patch, 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 For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4549) Distributed cache conflicts breaks backwards compatability
[ https://issues.apache.org/jira/browse/MAPREDUCE-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13612911#comment-13612911 ] Arun C Murthy commented on MAPREDUCE-4549: -- So, not sure why Oozie is still having problems... Roman, can you please re-check? > 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, 2.0.2-alpha >Reporter: Robert Joseph Evans >Assignee: Robert Joseph Evans >Priority: Blocker > Fix For: 0.23.5, 2.0.4-alpha > > Attachments: MAPREDUCE-4549-trunk.patch, 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 For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4549) Distributed cache conflicts breaks backwards compatability
[ https://issues.apache.org/jira/browse/MAPREDUCE-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13612910#comment-13612910 ] Arun C Murthy commented on MAPREDUCE-4549: -- Here is what I see on branch-2 from 'git log': commit 9aba3ebb2d455932981cc37fe8e3fa7a6ec4da82 Author: Alejandro Abdelnur Date: Tue Dec 11 19:50:32 2012 + MAPREDUCE-4549. Distributed cache conflicts breaks backwards compatability. (Robert Evans via tucu) git-svn-id: https://svn.apache.org/repos/asf/hadoop/common/branches/branch-2@1420363 13f79535-47bb-0310-9956-ffa450edef68 > 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, 2.0.2-alpha >Reporter: Robert Joseph Evans >Assignee: Robert Joseph Evans >Priority: Blocker > Fix For: 0.23.5, 2.0.4-alpha > > Attachments: MAPREDUCE-4549-trunk.patch, 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 For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4549) Distributed cache conflicts breaks backwards compatability
[ https://issues.apache.org/jira/browse/MAPREDUCE-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13565633#comment-13565633 ] Robert Joseph Evans commented on MAPREDUCE-4549: Do we want it on trunk? For example if I pass in -libjar a/foo.jar -libjar b/foo.jar in 1.0 everything will work and both foo.jar files will be on the classpath (I don't know why you would do this, but it is possible). Under YARN only one of them will even be shipped in the distributed cache, so there is no way at all for both of them to be on the classpath. With this patch it will output a warning message when a conflict occurs so people can try and fix the issue, but eventually we want to have the upper parts of the stack fix it, or we need to do what I was looking at doing initially and try to keep the colliding files separate by adding in support of sub directories in the distributed cache and using UUIDs. > 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, 2.0.2-alpha >Reporter: Robert Joseph Evans >Assignee: Robert Joseph Evans >Priority: Critical > Fix For: 2.0.3-alpha, 0.23.5 > > Attachments: MAPREDUCE-4549-trunk.patch, 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 For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4549) Distributed cache conflicts breaks backwards compatability
[ https://issues.apache.org/jira/browse/MAPREDUCE-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13565584#comment-13565584 ] Arun C Murthy commented on MAPREDUCE-4549: -- Has this been committed to trunk? Can we close this? > 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, 2.0.2-alpha >Reporter: Robert Joseph Evans >Assignee: Robert Joseph Evans >Priority: Critical > Fix For: 2.0.3-alpha, 0.23.5 > > Attachments: MAPREDUCE-4549-trunk.patch, 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 For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4549) Distributed cache conflicts breaks backwards compatability
[ https://issues.apache.org/jira/browse/MAPREDUCE-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13534033#comment-13534033 ] Robert Joseph Evans commented on MAPREDUCE-4549: I am fine with this being in branch-2. +1 > 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, 2.0.2-alpha >Reporter: Robert Joseph Evans >Assignee: Robert Joseph Evans >Priority: Critical > Fix For: 2.0.3-alpha, 0.23.5 > > Attachments: MAPREDUCE-4549-trunk.patch, 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 For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4549) Distributed cache conflicts breaks backwards compatability
[ https://issues.apache.org/jira/browse/MAPREDUCE-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13534033#comment-13534033 ] Robert Joseph Evans commented on MAPREDUCE-4549: I am fine with this being in branch-2. +1 > 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, 2.0.2-alpha >Reporter: Robert Joseph Evans >Assignee: Robert Joseph Evans >Priority: Critical > Fix For: 2.0.3-alpha, 0.23.5 > > Attachments: MAPREDUCE-4549-trunk.patch, 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 For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4549) Distributed cache conflicts breaks backwards compatability
[ https://issues.apache.org/jira/browse/MAPREDUCE-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13529263#comment-13529263 ] Alejandro Abdelnur commented on MAPREDUCE-4549: --- I'll be commit to branch-2 now. I'll wait till FRI noon to see if there are objections for committing this to trunk as well. > 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, 2.0.2-alpha >Reporter: Robert Joseph Evans >Assignee: Robert Joseph Evans >Priority: Critical > Fix For: 2.0.3-alpha, 0.23.5 > > Attachments: MAPREDUCE-4549-trunk.patch, 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 For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4549) Distributed cache conflicts breaks backwards compatability
[
https://issues.apache.org/jira/browse/MAPREDUCE-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13529250#comment-13529250
]
Hadoop QA commented on MAPREDUCE-4549:
--
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12560334/MAPREDUCE-4549-trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3118//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3118//console
This message is automatically generated.
> 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, 2.0.2-alpha
>Reporter: Robert Joseph Evans
>Assignee: Robert Joseph Evans
>Priority: Critical
> Fix For: 2.0.3-alpha, 0.23.5
>
> Attachments: MAPREDUCE-4549-trunk.patch, 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4549) Distributed cache conflicts breaks backwards compatability
[ https://issues.apache.org/jira/browse/MAPREDUCE-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13529234#comment-13529234 ] Alejandro Abdelnur commented on MAPREDUCE-4549: --- +1 pending jenkins. > 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, 2.0.2-alpha >Reporter: Robert Joseph Evans >Assignee: Robert Joseph Evans >Priority: Critical > Fix For: 2.0.3-alpha, 0.23.5 > > Attachments: MAPREDUCE-4549-trunk.patch, 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 For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4549) Distributed cache conflicts breaks backwards compatability
[ https://issues.apache.org/jira/browse/MAPREDUCE-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13529233#comment-13529233 ] Sandy Ryza commented on MAPREDUCE-4549: --- Reopened and uploaded a patch for trunk > 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, 2.0.2-alpha >Reporter: Robert Joseph Evans >Assignee: Robert Joseph Evans >Priority: Critical > Fix For: 2.0.3-alpha, 0.23.5 > > Attachments: MAPREDUCE-4549-trunk.patch, 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 For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4549) Distributed cache conflicts breaks backwards compatability
[ https://issues.apache.org/jira/browse/MAPREDUCE-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13449725#comment-13449725 ] Robert Joseph Evans commented on MAPREDUCE-4549: This JIRA has been lingering for a while. Alejandro, if you want this in branch-2 feel free to merge it in there and then resolve the JIRA, if not, I will just resolve the JIRA myself in a week or so. > 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 For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4549) Distributed cache conflicts breaks backwards compatability
[ 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
[jira] [Commented] (MAPREDUCE-4549) Distributed cache conflicts breaks backwards compatability
[ https://issues.apache.org/jira/browse/MAPREDUCE-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13437014#comment-13437014 ] Thomas Graves commented on MAPREDUCE-4549: -- +1 for 0.23 change. I'm going to commit this to 0.23. Arun, Alejandro - is there agreement on reverting MAPREDUCE-4503 from 2.0 and pulling this jira in there too? > 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
[jira] [Commented] (MAPREDUCE-4549) Distributed cache conflicts breaks backwards compatability
[ 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
[jira] [Commented] (MAPREDUCE-4549) Distributed cache conflicts breaks backwards compatability
[ https://issues.apache.org/jira/browse/MAPREDUCE-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436261#comment-13436261 ] Alejandro Abdelnur commented on MAPREDUCE-4549: --- No worries, no need to be sorry at all. Thanks for the details. IMO we should do the warning for Hadoop 2.x as well. Maybe in Hadoop 3.x converted to an exception. > 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
[jira] [Commented] (MAPREDUCE-4549) Distributed cache conflicts breaks backwards compatability
[ https://issues.apache.org/jira/browse/MAPREDUCE-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436226#comment-13436226 ] Robert Joseph Evans commented on MAPREDUCE-4549: Alejandro, Sorry you are right I was way too vague about who I talked with. "oozie people" does not really say anything about who they are or exactly what we talked about. Thank you for calling me out on this it was my bad. I spoke with Mohammad Islam and Virag Kothari. The extent of the conversation was primarily me clarifying the differences between 1.0 behavior of the distributed cache, the behavior of the cache in 2.0/0.23 prior to MAPREDUCE-4503, and its behavior post MAPREDUCE-4503. After that we talked about my proposed fix here, of turning the exception into a warning. They both were OK with that but wanted to perhaps look into having the error checking in 2.0 also happen as new items were added through the distributed cache APIs so that they could react to the issues on a per entry basis, instead of having the job submission fail. I thought this was reasonable and told them to file a JIRA against MAPREDUCE for it. I am happy for any other feedback people may have on the issues. The call was mostly for clarification. I probably didn't even need to mention it here, but since I did here is the full disclosure. > 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
[jira] [Commented] (MAPREDUCE-4549) Distributed cache conflicts breaks backwards compatability
[ https://issues.apache.org/jira/browse/MAPREDUCE-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436076#comment-13436076 ] Alejandro Abdelnur commented on MAPREDUCE-4549: --- Where was this discussed with the Oozie people? I'm not aware of this, I did not see any discussion in the oozie-dev@ alias. Would you please summarize the issue, how it affects Oozie and what is exactly the impact of leaving it incompatible in Hadoop 2? At first look I think we should keep backwards compatibility in Hadoop 2. > 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
[jira] [Commented] (MAPREDUCE-4549) Distributed cache conflicts breaks backwards compatability
[ https://issues.apache.org/jira/browse/MAPREDUCE-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436063#comment-13436063 ] Jason Lowe commented on MAPREDUCE-4549: --- +1 (non-binding), lgtm. > 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
[jira] [Commented] (MAPREDUCE-4549) Distributed cache conflicts breaks backwards compatability
[ https://issues.apache.org/jira/browse/MAPREDUCE-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435029#comment-13435029 ] Hudson commented on MAPREDUCE-4549: --- Integrated in Hadoop-Hdfs-0.23-Build #344 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/344/]) svn merge -c -1369197 Reverting: MAPREDUCE-4503 in branch-0.23 until MAPREDUCE-4549 can be addressed. (Revision 1372573) Result = SUCCESS bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1372573 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, 2.1.0-alpha, 3.0.0, 2.2.0-alpha >Reporter: Robert Joseph Evans >Assignee: Robert Joseph Evans >Priority: Critical > > I recently put in MAPREDUCE-4503 which went a bit too far, and broke > backwards compatibility with 1.0 in distribtued cache entries. This is to > change the behavior of the distributed cache to more closely match that of > 1.0. > In 1.0 when adding in a cache archive link the first link would win (be the > one that was created), not the last one as is the current behavior, when > there were conflicts then all of the others were ignored and just did not get > a symlink created, and finally no symlink was created for archives that had > did not have a fragment in the URL. > To simulate this behavior after we parse the cache files and cache archives > configuration we should walk through all conflicting links and pick the first > link that has a fragment to win. If no link has a fragment then it is just > the first link wins. All other conflicting links will have a warning an the > name of the link will be changed to include a UUID. If the same file is both > in the distributed cache as a cache file and a cache archive we will throw an > exception, for backwards compatibility. -- 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
