[
https://issues.apache.org/jira/browse/MAPREDUCE-5184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13676176#comment-13676176
]
Zhijie Shen commented on MAPREDUCE-5184:
----------------------------------------
Thanks for your review, [~sandyr]!
bq. Not sure that it makes sense to have this section and its predecessor
described as "Source Compatibility" vs. "Binary Compatibility". MAPREDUCE-4942,
for example, tracks changes that are binary-compatible, but not
source-compatible. Maybe it would make more sense to demarcate them as old API
vs. new API or incompatilities vs. compatibilities.
"Source Compatibility" here should indicate that if we cannot ensure binary
compatibility, then we should ensure source compatibility. In fact, not all
mapreduce APIs break binary compatibility. I'll clarify it in the next draft.
AFIAK, the patch of MAPREDUCE-4942 breaks the source compatibility to 0.23 not
MR1. If the patch is reverted, it is still binary compatibile to MR1, but not
source compatibile. However, it is worth noting it down.
> Document MR Binary Compatibility vis-a-vis hadoop-1 and hadoop-2
> ----------------------------------------------------------------
>
> Key: MAPREDUCE-5184
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5184
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Components: documentation
> Reporter: Arun C Murthy
> Assignee: Zhijie Shen
> Fix For: 2.1.0-beta
>
> Attachments: MAPREDUCE-5184.1.patch
>
>
--
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
