hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18405) Track scope for HBase-Spark module
Date Tue, 18 Jul 2017 21:06:00 GMT

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

Sean Busbey commented on HBASE-18405:

thanks for the quick turn around time on review!

bq. Module Layout should address hbase-spark-it module, I think.

I tried to get this across without specifying the actual modules used in implementation. It
meets all the requirements: is a new module, depends on old modules, only shows up as a reactor
module and in the assembly. Or do you mean I need to call out that the test stuff is subject
to the same constraints? Should I just go ahead an prescribe a layout?

bq. Did we actaully determine on the DISCUSS thread that we must support Spark 2.0+? We might
have to take a 2.1+ position, since I think there was some updates to work with Delegation
Tokens that didn't make it in right away and another goal is to have use case parity for secure

I thought that's what I read. I also thought works-correctly-enough made it into 2.0. lemme
go jira hunting.

bq. Milestone 5 backport could happen before Milestone 4 documentation is done. You said that
docs get updated closer to release time anyway in another thread on list.

Good point. I think the main reason I would like to list it first is to avoid a "we'll do
it later" that turns into not getting done. Worth the trouble?

bq. Integration Tests and Yetus tests are not included in any milestones. Combine with Unit
Test M2?

the integration test already exists, so I didn't keep it in a milestone (barring something
showing up in milestone 0's results).

milestone 1 covers the yetus changes, though it occurs to me now that it references docs that
won't exist until milestone 4.

Milestone 2 I meant to cover "write tests" basically. Maybe add a milestone after 4 that's
"ensure tests on asf jenkins" that includes the precommit updates?

> 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

View raw message