[
https://issues.apache.org/jira/browse/HBASE-18175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16060030#comment-16060030
]
Mike Drob commented on HBASE-18175:
-----------------------------------
Ah, yes, you're right, the parent pom in a multi-module project shouldn't have
any output artifacts.
Is the simplest thing to let you move forward to add a top-level hbase-spark-it
module? And then we can move things around once the mailing list discussion
reaches consensus.
Alternatively, I would support you doing something like:
hbase-spark
* pom
* hbase-spark-core (this is the current hbase-spark dir)
** pom
** src
* hbase-spark-it (this is your new module)
** pom
** src
But that might require a lot of shuffling of maven parts that are likely to end
up redone later anyway.
> 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)
