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

Vinod Kumar Vavilapalli commented on YARN-2789:
-----------------------------------------------

Sigh.

bq. Even though this is a private API, it will be used by downstream projects 
for testing. It'll be useful for this to be re-instated, maybe with a 
deprecated annotation, so that older versions of downstream projects can build 
against Hadoop 2.6.
I am inclined to have a separate _test-only_ public util API that keeps 
compatibility for tests. Rather than opening unwanted APIs up. I'll file a 
separate ticket for this, we need all YARN apps/frameworks to move to that API 
instead of these private unstable APIs.

For now, I am okay keeping a private compat for the APIs changed in YARN-2698.

> Re-instate the NodeReport.newInstance API modified in YARN-2968
> ---------------------------------------------------------------
>
>                 Key: YARN-2789
>                 URL: https://issues.apache.org/jira/browse/YARN-2789
>             Project: Hadoop YARN
>          Issue Type: Task
>            Reporter: Siddharth Seth
>            Priority: Critical
>
> Even though this is a private API, it will be used by downstream projects for 
> testing. It'll be useful for this to be re-instated, maybe with a deprecated 
> annotation, so that older versions of downstream projects can build against 
> Hadoop 2.6.
> create() being private is a problem for multiple other classes - ContainerId, 
> AppId etc, Container, NodeId ... Most classes on the client facing YARN APIs 
> are likely to be required for testing in downstream projects.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to