I agree with Anil that the spark-connector is woefully behind. The spark community is moving fast and the connector is based on a 2yo release. That code hasn’t seen much activity outside of rebranding. If we split it out into a different repo it just moves the problem—is anyone volunteering to not only fix the issues but advance the code base?
I vote for putting it on a feature branch and removing it from /develop. Anthony > On May 24, 2017, at 5:45 PM, Anilkumar Gingade <aging...@pivotal.io> wrote: > > The spark has come a long way after 1.3...The connector needs to be > upgraded to be meaningful.... > +1 for A > The existing code could be used as a reference in the future... > > -Anil. > > > On Wed, May 24, 2017 at 5:17 PM, Dan Smith <dsm...@pivotal.io> wrote: > >> Our geode-spark-connector needs some work. It's currently building against >> geode 1.0.0-incubating, because it has it's own separate build process. >> It's also somewhat out of date, we're building against spark 1.3. Is anyone >> actually using the spark connector? >> >> I think we need to get the spark connector out of the main geode repo since >> people are currently modifying code in the connector without even compiling >> it, since it's not linked into the gradle build. >> >> What do the geode devs think we should do with the geode-spark-connector? >> >> A) Move it into it's own repository, with it's own release cycle >> B) Delete it >> C) Other?? >> >> -Dan >>
