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

Ray Chiang commented on HADOOP-14534:
-------------------------------------

Still manually going through the JACC output.  So far, based on incident count 
and ignoring some of the issues which shouldn't cause compatibility issues 
(method added, added string), these are the ones affecting the widest count:

[HADOOP-10485  Remove dead classes in 
hadoop-streaming|https://issues.apache.org/jira/browse/HADOOP-10485]
[HADOOP-12504  Remove metrics 
v1|https://issues.apache.org/jira/browse/HADOOP-12504]
[HADOOP-10255  Rename HttpServer to HttpServer2 to retain older HttpServer in 
branch-2 for compatibility|https://issues.apache.org/jira/browse/HADOOP-10255]
[HADOOP-10465  Fix use of generics within 
SortedMapWritable|https://issues.apache.org/jira/browse/HADOOP-10465]
[HADOOP-12709  Cut s3:// from 
trunk|https://issues.apache.org/jira/browse/HADOOP-12709]
[HADOOP-13547  Optimize IPC client protobuf 
decoding|https://issues.apache.org/jira/browse/HADOOP-13547]
[HADOOP-12973  make DU 
pluggable|https://issues.apache.org/jira/browse/HADOOP-12973]

It is important to note that this is ignoring any private/public annotation.

> [Umbrella] API related cleanup for Hadoop 3
> -------------------------------------------
>
>                 Key: HADOOP-14534
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14534
>             Project: Hadoop Common
>          Issue Type: Task
>    Affects Versions: 3.0.0-alpha3
>            Reporter: Ray Chiang
>            Assignee: Ray Chiang
>
> Creating this umbrella JIRA for tracking various API related issues that need 
> to be properly tracked, adjusted, or documented before Hadoop 3 release.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to