[ 
https://issues.apache.org/jira/browse/HBASE-18405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16092207#comment-16092207
 ] 

Mike Drob commented on HBASE-18405:
-----------------------------------

If we have multiple modules for a cartesian product of spark and scala 
versions, do we need corresponding IT modules for each of them? Can we run the 
same ITs several times in a matrix within maven? Do we want to reserve that for 
a profile? What do we expect daily developers to do, what do we expect RMs to 
do?

bq. I thought that's what I read. I also thought works-correctly-enough made it 
into 2.0. lemme go jira hunting.
SPARK-14743 is the one I'm thinking of.

bq. avoid a "we'll do it later" that turns into not getting done. Worth the 
trouble?
If you mark it a blocker for 2.0, it should get done, no?

bq. the integration test already exists, so I didn't keep it in a milestone 
(barring something showing up in milestone 0's results).
_One_ integration test exists. Do you think this provides sufficient coverage?
Would love to see the IT get run with monkeys also, not sure if it currently 
supports that.

bq. Maybe add a milestone after 4 that's "ensure tests on asf jenkins" that 
includes the precommit updates?
Didn't you already do this?


Scaladoc update is missing from milestones. Likely M4.


> Track scope for HBase-Spark module
> ----------------------------------
>
>                 Key: HBASE-18405
>                 URL: https://issues.apache.org/jira/browse/HBASE-18405
>             Project: HBase
>          Issue Type: Task
>          Components: spark
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>             Fix For: 1.4.0, 2.0.0-beta-1
>
>         Attachments: Apache HBase - Apache Spark Integration Scope.pdf
>
>
> Start with [\[DISCUSS\]  status of and plans for our hbase-spark integration 
> |https://lists.apache.org/thread.html/fd74ef9b9da77abf794664f06ea19c839fb3d543647fb29115081683@%3Cdev.hbase.apache.org%3E]
>  and formalize into a scope document for bringing this feature into a release.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to