which is the default action
> >> anyways).
> >> Thanks
> >> Devaraj
> >>
> >> From: Sean Busbey <bus...@apache.org>
> >> Sent: Wednesday, November 16, 2016 9:49 AM
> >> To: dev
> &
araj
>>
>> From: Sean Busbey <bus...@apache.org>
>> Sent: Wednesday, November 16, 2016 9:49 AM
>> To: dev
>> Subject: [DISCUSS] hbase-spark module in branch-1 and branch-2
>>
>> Hi folks!
>>
>> With
nd
> >> his
> >>> opinion was that the hbase-spark module as it currently stands can be
> >> used
> >>> by downstream users to do basic stuff and to try some simple things
> out,
> >>> etc. The integration is improving.
> >>>
be
>> used
>>> by downstream users to do basic stuff and to try some simple things out,
>>> etc. The integration is improving.
>>> I think we should get what we have in 2.0 (which is the default action
>>> anyways).
>>> Thanks
>>> Devaraj
yways).
> > Thanks
> > Devaraj
> >
> > From: Sean Busbey <bus...@apache.org>
> > Sent: Wednesday, November 16, 2016 9:49 AM
> > To: dev
> > Subject: [DISCUSS] hbase-spark module in branch-1 and branch-2
> >
ays).
> Thanks
> Devaraj
>
> From: Sean Busbey <bus...@apache.org>
> Sent: Wednesday, November 16, 2016 9:49 AM
> To: dev
> Subject: [DISCUSS] hbase-spark module in branch-1 and branch-2
>
> Hi folks!
>
> With 2.0 releases coming up, I'd like to revive ou
in 2.0 (which is the default action anyways).
Thanks
Devaraj
From: Sean Busbey <bus...@apache.org>
Sent: Wednesday, November 16, 2016 9:49 AM
To: dev
Subject: [DISCUSS] hbase-spark module in branch-1 and branch-2
Hi folks!
With 2.0 releases coming u
Hi folks!
With 2.0 releases coming up, I'd like to revive our prior discussion
on the readiness of the hbase-spark module for downstream users.
We've had a ticket for tracking the milestones set up for inclusion in
branch-1 releases for about 1.5 years:
