After HBASE-16179 gets reviewed / committed, I should be able to take on other high priority Spark connector issues.
Cheers On Wed, Jan 18, 2017 at 12:30 PM, Sean Busbey <bus...@apache.org> wrote: > I don't doubt that downstream users could "try out" our integration > using what currently exists in the branch-2. However, we already had > community consensus on what is necessary for our downstream folks to > have a good experience with a ready-for-production feature. I don't > see why we should subject them to a lower bar in a branch-2 release > than we would have in a branch-1 release just because we're starting > up a new major version. > > The work in HBASE-16179 is certainly a blocker given the rising > popularity of Spark 2.0 (thanks Ted for getting that work under way, I > hope we get sufficient review bandwidth to get it finished), but it's not > everything; e.g. we don't have regression checks in place for the > things that show up in our docs. > > - > busbey > > On Sat, Jan 14, 2017 at 4:52 PM, Ted Yu <yuzhih...@gmail.com> wrote: > > I agree with Devaraj's assessment w.r.t. hbase-spark module in master > > (which is becoming branch-2). > > > > Cheers > > > > > > > > On Mon, Nov 21, 2016 at 11:46 AM, Devaraj Das <d...@hortonworks.com> > wrote: > > > >> Hi Sean, I did a quick check with someone from the Spark team here and > 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. > >> I think we should get what we have 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 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: > >> > >> https://issues.apache.org/jira/browse/HBASE-14160 > >> > >> We still haven't gotten all of the blocker issues completed, AFAIK. > >> > >> Is anyone interested in volunteering to knock the rest of these out? > >> > >> If they aren't, shall we plan to leave hbase-spark in master and > >> revert it from branch-2 once it forks for the HBase 2.0 release line? > >> > >> This feature isn't a blocker for 2.0; just as we've been planning to > >> add the hbase-spark module to some 1.y release we can also include it > >> in a 2.1+ release. > >> > >> This does appear to be a feature our downstream users could benefit > >> from, so I'd hate to continue the current situation where no official > >> releases include it. This is especially true now that we're looking at > >> ways to handle changes between Spark 1.6 and Spark 2.0 in HBASE-16179. > >> > >> - > >> busbey > >> > >> >
