hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5130) Mark ContainerStatus and NodeReport as evolving
Date Mon, 13 Jun 2016 14:59:21 GMT

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

Steve Loughran commented on YARN-5130:
--------------------------------------

What I really want is "changes to the YARN APIs not to break my code". While tagging things
as unstable provides a warning, and accurate documentation of where we are today, it's not
quite what I'd expect from the public APIs

> Mark ContainerStatus and NodeReport as evolving
> -----------------------------------------------
>
>                 Key: YARN-5130
>                 URL: https://issues.apache.org/jira/browse/YARN-5130
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: yarn
>    Affects Versions: 2.8.0
>            Reporter: Steve Loughran
>            Assignee: Gergely Novák
>            Priority: Minor
>         Attachments: YARN-5130.001.patch
>
>
> It turns out that slider won't build as the {{ContainerStatus}} and {{NodeReport}} classes
have added more abstract methods, so breaking the mock objects.
> While it is everyone's freedom to change things, these classes are both tagged
> {code}
> @Public
> @Stable
> {code}
> Given they aren't stable, can someone mark them as {{@Evolving}}? That way when downstream
code breaks, we can be less disappointed



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

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message