[
https://issues.apache.org/jira/browse/YARN-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15987149#comment-15987149
]
Junping Du commented on YARN-5007:
----------------------------------
bq. If 3.0 is not a good time to remove deprecated method, when is a good time?
Deprecated means this method is not recommended to use, and no promise of
supporting well in following releases. That doesn't mean we have to
remove/break these methods. For the safest time of removing, I would suggest to
wait for another major release. Otherwise, case here will happen again and
again.
bq. -1 on reverting YARN-3573.
Technically, in apache way, -1 doesn't work for any reverting work - no matter
binding or non-binding. However, after thinking again, I would agree keeping
YARN-3573 there is better.
Thanks [~ajisakaa] for the revert work. Let's resolve this JIRA as won't fix or
after.
> Remove deprecated constructors of MiniYARNCluster and MiniMRYarnCluster
> -----------------------------------------------------------------------
>
> Key: YARN-5007
> URL: https://issues.apache.org/jira/browse/YARN-5007
> Project: Hadoop YARN
> Issue Type: Test
> Reporter: Andras Bokor
> Assignee: Andras Bokor
> Labels: oct16-easy
> Attachments: YARN-5007.01.patch, YARN-5007.02.patch,
> YARN-5007.03.patch
>
>
> MiniYarnCluster has a deprecated constructor which is called by the other
> constructors and it causes javac warnings during the build.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
