[
https://issues.apache.org/jira/browse/HBASE-7938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13596420#comment-13596420
]
Nick Dimiduk commented on HBASE-7938:
-------------------------------------
Yeah, I like how that test is broken out. However, I think having a main per
test and also being able to run from IntegrationTestsDriver is redundant. The
reality is, the runtime classpath for these tests is a little bit prickly (see
HBASE-7971) and while it would be great for a user to be able to run the IT
suite as a smoke-test of an upgrade or fresh install, we don't exactly make
that easy right now.
My thinking is that a test would configure itself via the run method, no
additional arguments necessary. The biggest thing is hooking into Hadoop's
GenericOptionsParser in order to set up an external -conf and any -D overrides
the user wants to impose.
> 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
> Reporter: Nick Dimiduk
> Fix For: 0.95.0, 0.98.0, 0.94.7
>
>
> 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
