[
https://issues.apache.org/jira/browse/YARN-5130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15329527#comment-15329527
]
Sunil G commented on YARN-5130:
-------------------------------
Yes. I agree with your point. There should be a strict notion while making
changes on a Stable interface especially to those exposed to client and other
modules. We could have some test cases to detect this, still a hack in test
cases could take us back to original problem.
> 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: [email protected]
For additional commands, e-mail: [email protected]
