[
https://issues.apache.org/jira/browse/HBASE-18175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16059959#comment-16059959
]
Yi Liang commented on HBASE-18175:
----------------------------------
Hi Mike,
Thanks for asking, i am now waiting for the final layout of hbase-spark
module. Since right now, if I add hbase-spark-it under hbase spark, it has
below layout.
hbase-spark
-----------src
-----------pom
-----------hbase-spark-it
---------------src
---------------pom
And if we have layout above, there is no hbase-spark.jar created in
hbase-spark/target after I mvn package, so the unit test and it test can not
find related jars.
if we have something below, actually a place to store hbase-spark.jar,
like(hbase-spark-2.0/target). The tests then can run successfully.
hbase-spark
-----------src
-----------pom
-----------hbase-spark-2.0
-----------hbase-spark-it
---------------src
---------------pom
So I am still waiting for the final layout, then I can decide to have a new
hbase-spark-it module or just directly put it into hbase-spark module
> Add hbase-spark integration test into hbase-it
> ----------------------------------------------
>
> Key: HBASE-18175
> URL: https://issues.apache.org/jira/browse/HBASE-18175
> Project: HBase
> Issue Type: Test
> Components: spark
> Reporter: Yi Liang
> Assignee: Yi Liang
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: hbase-18175-v1.patch
>
>
> After HBASE-17574, all test under hbase-spark are regarded as unit test, and
> this jira will add integration test of hbase-spark into hbase-it. This patch
> run same tests as mapreduce.IntegrationTestBulkLoad, just change mapreduce to
> spark.
> test in Maven:
> mvn verify -Dit.test=IntegrationTestSparkBulkLoad
> test on cluster:
> spark-submit --class
> org.apache.hadoop.hbase.spark.IntegrationTestSparkBulkLoad
> HBASE_HOME/lib/hbase-it-2.0.0-SNAPSHOT-tests.jar
> -Dhbase.spark.bulkload.chainlength=500000 -m slowDeterministic
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)