[
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
