Re: What to do with the geode-spark-connector

[Anthony Baker]

We have suggestions to split into a separate repo (along with fixing it) and 
removing it altogether.  In the spirit of ASF do-ocracy, are there any 
volunteers to take on the former?

This has an affect on the 1.2.0 release since the spark connector is part of 
the release but needs further work before it is shippable even in its current 
out-dated form.

Anthony

> On May 25, 2017, at 9:21 AM, Lynn Hughes-Godfrey  
> wrote:
> 
> I agree with Mark and Anthony ...
> +1 to deleting this altogether.
> 
> On Thu, May 25, 2017 at 9:12 AM, John Blum  wrote:
> 
>> Perhaps the bigger question is, is anyone even using the connector?  No
>> sense in supporting something that isn't used by anyone when those efforts
>> could be utilized elsewhere (e.g. Redis Protocol Adapter/Data Structures).
>> 
>> On Thu, May 25, 2017 at 8:52 AM, Mark Bretl  wrote:
>> 
>>> 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 
>>> 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 
>>> wrote:
>> 
>> +1 for A
>> 
>> On May 24, 2017 6:48 PM, "Kirk Lund"  wrote:
>> 
>>> +1 for A
>>> 
>>> On Wed, May 24, 2017 at 5:50 PM, Jianxia Chen 
 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 
 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
> 
 
>>> 
> 
> 
 
>>> 
>> 
>> 
>> 
>> --
>> -John
>> john.blum10101 (skype)
>> 

Re: What to do with the geode-spark-connector

[Lynn Hughes-Godfrey]

I agree with Mark and Anthony ...
+1 to deleting this altogether.

On Thu, May 25, 2017 at 9:12 AM, John Blum  wrote:

> Perhaps the bigger question is, is anyone even using the connector?  No
> sense in supporting something that isn't used by anyone when those efforts
> could be utilized elsewhere (e.g. Redis Protocol Adapter/Data Structures).
>
> On Thu, May 25, 2017 at 8:52 AM, Mark Bretl  wrote:
>
> > 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 
> > 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 
> > wrote:
> > > > >
> > > > > +1 for A
> > > > >
> > > > > On May 24, 2017 6:48 PM, "Kirk Lund"  wrote:
> > > > >
> > > > >> +1 for A
> > > > >>
> > > > >> On Wed, May 24, 2017 at 5:50 PM, Jianxia Chen 
> > > 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 
> > > 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
> > > > 
> > > > >>>
> > > > >>
> > > >
> > > >
> > >
> >
>
>
>
> --
> -John
> john.blum10101 (skype)
>

Re: What to do with the geode-spark-connector

[John Blum]

Perhaps the bigger question is, is anyone even using the connector?  No
sense in supporting something that isn't used by anyone when those efforts
could be utilized elsewhere (e.g. Redis Protocol Adapter/Data Structures).

On Thu, May 25, 2017 at 8:52 AM, Mark Bretl  wrote:

> 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 
> 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 
> wrote:
> > > >
> > > > +1 for A
> > > >
> > > > On May 24, 2017 6:48 PM, "Kirk Lund"  wrote:
> > > >
> > > >> +1 for A
> > > >>
> > > >> On Wed, May 24, 2017 at 5:50 PM, Jianxia Chen 
> > 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 
> > 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
> > > 
> > > >>>
> > > >>
> > >
> > >
> >
>



-- 
-John
john.blum10101 (skype)

Re: What to do with the geode-spark-connector

[Mark Bretl]

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 
wrote:

> +1 on A
>
> On Thu, May 25, 2017 at 8:21 AM, Michael William Dodge 
> wrote:
>
> > +1 for A
> >
> > > On 24 May, 2017, at 21:30, Jared Stewart  wrote:
> > >
> > > +1 for A
> > >
> > > On May 24, 2017 6:48 PM, "Kirk Lund"  wrote:
> > >
> > >> +1 for A
> > >>
> > >> On Wed, May 24, 2017 at 5:50 PM, Jianxia Chen 
> 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 
> 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
> > 
> > >>>
> > >>
> >
> >
>

Re: What to do with the geode-spark-connector

[Ernest Burghardt]

+1 on A

On Thu, May 25, 2017 at 8:21 AM, Michael William Dodge 
wrote:

> +1 for A
>
> > On 24 May, 2017, at 21:30, Jared Stewart  wrote:
> >
> > +1 for A
> >
> > On May 24, 2017 6:48 PM, "Kirk Lund"  wrote:
> >
> >> +1 for A
> >>
> >> On Wed, May 24, 2017 at 5:50 PM, Jianxia Chen  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  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
> 
> >>>
> >>
>
>

Re: What to do with the geode-spark-connector

[Bruce Schuchardt]

+1

On Thu, May 25, 2017 at 8:15 AM, Udo Kohlmeyer  wrote:

> +1 to moving it from develop to it's own repo and gradle build. The
> spark-connector is another quintessential project that should be treated as
> an external module to geode.
>
>
> On 5/25/17 07:58, Anthony Baker wrote:
>
>> 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 
>>> 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  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


>

Re: What to do with the geode-spark-connector

[Michael William Dodge]

+1 for A

> On 24 May, 2017, at 21:30, Jared Stewart  wrote:
> 
> +1 for A
> 
> On May 24, 2017 6:48 PM, "Kirk Lund"  wrote:
> 
>> +1 for A
>> 
>> On Wed, May 24, 2017 at 5:50 PM, Jianxia Chen  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  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
 
>>> 
>> 

Re: What to do with the geode-spark-connector

[Udo Kohlmeyer]

+1 to moving it from develop to it's own repo and gradle build. The 
spark-connector is another quintessential project that should be treated 
as an external module to geode.



On 5/25/17 07:58, Anthony Baker wrote:

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  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  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

Re: What to do with the geode-spark-connector

[Anthony Baker]

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  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  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
>> 

Re: What to do with the geode-spark-connector

[Kirk Lund]

+1 for A

On Wed, May 24, 2017 at 5:50 PM, Jianxia Chen  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  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
> >
>

Re: What to do with the geode-spark-connector

[Jianxia Chen]

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  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
>

Re: What to do with the geode-spark-connector

[Anilkumar Gingade]

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  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
>

What to do with the geode-spark-connector

[Dan Smith]

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