[
https://issues.apache.org/jira/browse/HBASE-7938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13597375#comment-13597375
]
nkeywal commented on HBASE-7938:
--------------------------------
I'm +1 of course.
I don't really know the IntegrationTestsDriver, I use maven to run the
integration tests (I'm not saying it's a good thing, actually may be it's a bad
thing). I will have a look.
If it has not changed recently, we don't start a mini map reduce cluster when
we do a start-hbase not distributed. We should add it may be, to ease manual
tests?
Following the work done in HBASE-7840, we could also add the start/stop of the
map reduce part.
Then the integration tests dependending on map reduce could start a real
cluster. For the path, I don't know: if we include the test code in HBase, it
will have copied all other the place anyway, so we won't be able to check this.
The code would have to be quite smart to explicitly ask maven to do nothing
about it.
> 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
