I have similar thoughts as Anthony on this issue. No matter if it is a separate repo or branch I think it will be left behind.
I think the bigger question is does this community want to continue to support the connector? --Mark On Thu, May 25, 2017 at 8:34 AM Ernest Burghardt <eburgha...@pivotal.io> wrote: > +1 on A > > On Thu, May 25, 2017 at 8:21 AM, Michael William Dodge <mdo...@pivotal.io> > wrote: > > > +1 for A > > > > > On 24 May, 2017, at 21:30, Jared Stewart <jstew...@pivotal.io> wrote: > > > > > > +1 for A > > > > > > On May 24, 2017 6:48 PM, "Kirk Lund" <kl...@apache.org> wrote: > > > > > >> +1 for A > > >> > > >> On Wed, May 24, 2017 at 5:50 PM, Jianxia Chen <jc...@pivotal.io> > wrote: > > >> > > >>> I prefer option A: Move it into it's own repository, with it's own > > >> release > > >>> cycle. > > >>> > > >>> 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 > > >>>> > > >>> > > >> > > > > >
