[
https://issues.apache.org/jira/browse/YARN-6022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15771737#comment-15771737
]
Karthik Kambatla commented on YARN-6022:
----------------------------------------
bq. For example, with this change, we need to make AbstractResourceRequest to
be public/stable
Why? Why not leave the AbstractResourceRequest as @Public @Unstable? That way,
users will not be able to use AbstractResourceRequest directly but the methods
on ResourceRequest remain Public-Stable.
I may be missing the incompatibility part. [~leftnoteasy] - mind clarifying it
for me may be with an example of what fails to work now?
> Revert changes of AbstractResourceRequest
> -----------------------------------------
>
> Key: YARN-6022
> URL: https://issues.apache.org/jira/browse/YARN-6022
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Wangda Tan
> Priority: Blocker
>
> YARN-5774 added AbstractResourceRequest to make easier internal scheduler
> change, this is not a correct approach: For example, with this change, we
> need to make AbstractResourceRequest to be public/stable. And end users can
> use it like:
> {code}
> AbstractResourceRequest request = ...
> request.setCapability(...)
> {code}
> But AbstractResourceRequest should not be visible by application at all.
> We need to revert it from branch-2.8 / branch-2 / trunk.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
