[
https://issues.apache.org/jira/browse/YARN-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15292224#comment-15292224
]
Andras Bokor commented on YARN-5007:
------------------------------------
[~jzhuge]
This issue came up on YARN-4494.
Either {{MiniDFSCluster}} or {{MiniMRYarnCluster}} have the same problem . What
do you think? Should they be fixed in one (this) JIRA or should I separate them
into 2/3 JIRAs? I have either pros:
* Basically it is one problem but on individual classes
* Less work for committers
* Less administration
* {{MiniMRYarnCluster}} calls {{MiniYarnCluster}} so {{MiniMRYarnCluster}}
needs to be changed anyway
or cons:
* Patch size bigger
* {{MiniDFSCluster}} belongs to HDFS and it is a YARN ticket
* {{MiniMRYarnCluster}} belongs to MAPREDUCE and it is a YARN ticket
How about include {{MiniMRYarnCluster}} and {{MiniYarnCluster}} in this JIRA
and {{MiniDFSCluster}} in another in HDFS project?
What do you think?
> MiniYarnCluster contains deprecated constructor which is called by the other
> constructors
> -----------------------------------------------------------------------------------------
>
> Key: YARN-5007
> URL: https://issues.apache.org/jira/browse/YARN-5007
> Project: Hadoop YARN
> Issue Type: Test
> Components: timelineserver
> Affects Versions: 2.6.0
> Reporter: Andras Bokor
> Assignee: Andras Bokor
> Priority: Minor
> Fix For: 2.8.0
>
>
> 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.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
