You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Nick Dimiduk (JIRA)" <ji...@apache.org> on 2013/03/07 21:29:12 UTC

[jira] [Commented] (HBASE-7938) Add integration test for various MapReduce workflows

    [ https://issues.apache.org/jira/browse/HBASE-7938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13596327#comment-13596327 ] 

Nick Dimiduk commented on HBASE-7938:
-------------------------------------

In many cases, we already have decent coverage in the existing unit tests. The trouble is, some bugs cannot be caught using the classpath generated by Maven because it's too generous about including jars on our behalf. Rather than re-implementing bits from existing unit tests, I'd like to modify IntegrationTestsDriver to accept any class that implements Tool. With that change, I can modify the existing unit tests to implement a run method where the prickly scenarios can be run against an external cluster, as configured by IntegratoinTestsDriver. I'm hoping this will minimize changes to existing test code and also minimize code duplication.

What do you think?
                
> Add integration test for various MapReduce workflows
> ----------------------------------------------------
>
>                 Key: HBASE-7938
>                 URL: https://issues.apache.org/jira/browse/HBASE-7938
>             Project: HBase
>          Issue Type: Bug
>          Components: mapreduce
>    Affects Versions: 0.96.0, 0.94.5
>            Reporter: Nick Dimiduk
>
> We have existing unit tests for smoke-testing the packaged MR jobs, however they do not create a runtime environment that is true to running on a real MR cluster. This is particularly true in regard to classpaths (HBASE-7934) but also other static state (HBASE-4802). An integration test that can be pointed to run on a pseudo-distributed Hadoop deployed on localhost would find these kinds of problems.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira