[
https://issues.apache.org/jira/browse/HBASE-7938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13601513#comment-13601513
]
Nick Dimiduk commented on HBASE-7938:
-------------------------------------
bq. change the test method name generateAndLoad() to start with "test" per
convention
Can do.
bq. One difference between running from command line and running by:
HBASE_CLASSPATH=hbase-it/target/hbase-it-0.97-SNAPSHOT-tests.jar bin/hbase
org.apache.hadoop.hbase.IntegrationTestsDriver -test IntegrationTestImportTsv
is that the latter will run all of the tests (both TestImportTsv and
IntegrationTestImportTsv) while the former will only run the generateAndLoad()
test
That's true. I considered using a reflection loop to execute all of the tests
under this scenario, but I decided it wasn't really worth it. Maybe it could be
done by programmatically driving JUnit, but getting the conf objects correct
looks surprisingly difficult.
bq. Also got this exception while running from IntegrationTestsDriver
This looks like the IntegrationTestingUtility didn't clean up the test
directory after a run. Did you kill or have an error on a previous run?
> Add integration test for ImportTsv/LoadIncrementalHFiles workflow
> -----------------------------------------------------------------
>
> Key: HBASE-7938
> URL: https://issues.apache.org/jira/browse/HBASE-7938
> Project: HBase
> Issue Type: Sub-task
> Components: mapreduce
> Reporter: Nick Dimiduk
> Assignee: Nick Dimiduk
> Fix For: 0.95.0, 0.98.0
>
> Attachments:
> 0001-HBASE-7938-Add-integration-test-for-ImportTsv-LoadIn.patch
>
>
> 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
