You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Vinod K V (JIRA)" <ji...@apache.org> on 2009/09/04 05:54:57 UTC
[jira] Created: (HADOOP-6237) Move common specific tests
TestReflectionUtils and TestRunJar out of mapred into common
Move common specific tests TestReflectionUtils and TestRunJar out of mapred into common
---------------------------------------------------------------------------------------
Key: HADOOP-6237
URL: https://issues.apache.org/jira/browse/HADOOP-6237
Project: Hadoop Common
Issue Type: Bug
Components: test
Reporter: Vinod K V
Fix For: 0.21.0
These two classes are common specific and so have to be moved out of mapred.
As commented by Tom here (https://issues.apache.org/jira/browse/HADOOP-6230?focusedCommentId=12751058&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12751058), TestReflectionUtils has a single test testSetConf() to test backward compatibility of ReflectionUtils for JobConfigurable objects. TestReflectionUtils can be spilt into two tests - one on common and one in mapred - this single test may reside in mapred till the mapred package is removed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-6237) Move common specific part of the test
TestReflectionUtils out of mapred into common
Posted by "Vinod K V (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod K V updated HADOOP-6237:
------------------------------
Description: As commented by Tom here (https://issues.apache.org/jira/browse/HADOOP-6230?focusedCommentId=12751058&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12751058), TestReflectionUtils has a single test testSetConf() to test backward compatibility of ReflectionUtils for JobConfigurable objects. TestReflectionUtils can be spilt into two tests - one on common and one in mapred - this single test may reside in mapred till the mapred package is removed. (was: These two classes are common specific and so have to be moved out of mapred.
As commented by Tom here (https://issues.apache.org/jira/browse/HADOOP-6230?focusedCommentId=12751058&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12751058), TestReflectionUtils has a single test testSetConf() to test backward compatibility of ReflectionUtils for JobConfigurable objects. TestReflectionUtils can be spilt into two tests - one on common and one in mapred - this single test may reside in mapred till the mapred package is removed.)
Summary: Move common specific part of the test TestReflectionUtils out of mapred into common (was: Move common specific tests TestReflectionUtils and TestRunJar out of mapred into common)
Apparently (as Arun comments here at https://issues.apache.org/jira/browse/MAPREDUCE-727?focusedCommentId=12728372&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12728372) RunJar itself is going to be moved into mapred. So TestRunJar can reside in mapreduce. Changing the scope and subject of this issue to reflect the same.
> Move common specific part of the test TestReflectionUtils out of mapred into common
> -----------------------------------------------------------------------------------
>
> Key: HADOOP-6237
> URL: https://issues.apache.org/jira/browse/HADOOP-6237
> Project: Hadoop Common
> Issue Type: Bug
> Components: test
> Reporter: Vinod K V
> Fix For: 0.21.0
>
>
> As commented by Tom here (https://issues.apache.org/jira/browse/HADOOP-6230?focusedCommentId=12751058&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12751058), TestReflectionUtils has a single test testSetConf() to test backward compatibility of ReflectionUtils for JobConfigurable objects. TestReflectionUtils can be spilt into two tests - one on common and one in mapred - this single test may reside in mapred till the mapred package is removed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.