[
https://issues.apache.org/jira/browse/MAPREDUCE-5184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680829#comment-13680829
]
Karthik Kambatla commented on MAPREDUCE-5184:
---------------------------------------------
bq. Recently we conducted intensive research and work on the APIs to fix the
problems.
IMO, we should avoid references to time (recently).The patch documents the
state between hadoop-1 and hadoop-2 for eternity :)
Think it might be useful to explain (at least briefly) what we mean by binary
and source compatibility. I am particular concerned about source compatibility
- I think we need to be explicit in what we mean. From what I have learnt
recently (while working on HADOOP-9517), source compatibility is not easy to
guarantee in Java (e.g. adding a class/method can technically break wildcard
imports conflicting with user classes/methods with the same name
(package/class/method)) and even the JDK doesn't try to guarantee it. See
http://www.oracle.com/technetwork/java/javase/compatibility-417013.html#source
and http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs
> 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, MAPREDUCE-5184.2.patch,
> MAPREDUCE-5184.3.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
