You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Chris Douglas (JIRA)" <ji...@apache.org> on 2009/03/26 09:57:55 UTC

[jira] Updated: (HADOOP-5164) Subclasses of ClusterMapReduceTestCase can't easily add new configuration parameters

     [ https://issues.apache.org/jira/browse/HADOOP-5164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Douglas updated HADOOP-5164:
----------------------------------

    Status: Open  (was: Patch Available)

For a cluster shared between tests, wouldn't the correct idiom use TestSetup, as in TestAppend3, TestReduceFetch, etc.? If each test needs a different set of parameters, it's not clear to me why one wouldn't simply create a Configuration with these parameters, and start Mini\*Cluster with it...

> 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.2.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.