[HADOOP-5164] Subclasses of ClusterMapReduceTestCase can't easily add new configuration parameters

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: test
• Hadoop Flags: Incompatible change

Release Note

Modified the behavior of ClusterMapReduceTestCase so that setupCluster() is no longer called automatically in TestCase.setUp(). Now, you must explicitly call setupCluster() for each test you wish to run (or you can share a single cluster among several tests).

• Assignee: Unassigned
• Reporter: George Porter
• Created: 04/Feb/09 02:59
• Updated: 26/Mar/09 08:56

Description

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.