[
https://issues.apache.org/jira/browse/HADOOP-5164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
George Porter updated HADOOP-5164:
----------------------------------
Attachment: HADOOP-5164.1.patch
With this patch, every test case that is in a subclass of
ClusterMapReduceTestCase now explicitly calls startCluster(). This makes it
possible to create test case subclasses of ClusterMapReduceTestCase that use
alternative parameters to the cluster. It also makes it possible to have
different clusters in your test cases that have different parameters.
> Subclasses of ClusterMapReduceTestCase can't easily add new configuration
> parameters
> ------------------------------------------------------------------------------------
>
> Key: HADOOP-5164
> URL: https://issues.apache.org/jira/browse/HADOOP-5164
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Reporter: George Porter
> Attachments: HADOOP-5164.1.patch, HADOOP-5164.patch
>
>
> Currently there is not a clean way for subclasses of ClusterMapReduceTestCase
> to add to the JobConf used to start the cluster daemons.
> The startCluster() method does take a Properties object that is added to the
> JobConf used to the start the daemons. However, startCluster() is called
> from JUnit inside the setUp() method, which sets this parameter to be null.
> If you try to override setUp() in a subclass of ClusterMapReduceTestCase,
> then you won't be able to invoke the TestCase.setUp() ancestor without
> calling ClusterMapReduceTestCase's setUp() (which will pass in the null
> parameter). On the other hand, if you just call startCluster() within your
> test method, then you would be starting up a cluster that was already started.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
