You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@arrow.apache.org by Andy Grove <an...@gmail.com> on 2022/05/16 13:55:00 UTC
[VOTE] [Rust] Move Ballista to new arrow-ballista repository
I would like to propose that we move the Ballista project to a new
top-level *arrow-ballista* repository.
The rationale for this (copied from the GitHub issue [1]) is:
-
Decouple release process for DataFusion and Ballista
-
Allow each project to have top-level documentation and user guides that
are targeting the appropriate audience
-
Reduce issue tracking and PR review burden for DataFusion maintainers
who are not as interested in Ballista
-
Help avoid accidental circular dependencies being introduced between the
projects (such as [3])
-
Helps formalize the public API for DataFusion that other query engines
should be using
There is a design docment [3] that outlines the plan for implementing this.
Only votes from PMC members are binding, but all members of the community
are encouraged to test the release and vote with "(non-binding)". The vote
will run for at least 72 hours.
[ ] +1 Proceed with moving Ballista to a new arrow-ballista repository [ ]
+0
[ ] -1 Do not proceed with moving Ballista to a new arrow-ballista
repository because ...
Here is my vote:
+1 (binding)
[1] https://github.com/apache/arrow-datafusion/issues/2502
[2] https://github.com/apache/arrow-datafusion/issues/2433
[3]
https://docs.google.com/document/d/1jNRbadyStSrV5kifwn0khufAwq6OnzGczG4z8oTQJP4/edit?usp=sharing
RE: [VOTE] [Rust] Move Ballista to new arrow-ballista repository
Posted by Matthew Turner <ma...@outlook.com>.
Thanks for driving this Andy! I'm very excited to about the next phase of both these projects.
-----Original Message-----
From: Andy Grove <an...@gmail.com>
Sent: Thursday, May 19, 2022 10:32 AM
To: dev <de...@arrow.apache.org>
Subject: Re: [VOTE] [Rust] Move Ballista to new arrow-ballista repository
With 7 binding votes, and 3 non-binding votes, the vote passes. Thank you to everyone who put the time into reading the proposal and voting on this issue.
I will go ahead and create the new repo and will work with the DataFusion & Ballista developers over the next couple weeks to implement this. I hope to have this working smoothly before the next major release of DataFusion, which we plan on releasing around one month from now.
Thanks,
Andy.
On Thu, May 19, 2022 at 8:28 AM Andy Grove <an...@gmail.com> wrote:
> Per Matthew's point about feedback from Ballista devs, I have been
> discussing this with yahoNanJing in the GitHub issue that was linked
> to in the start of this email thread and it seems they are comfortable
> with moving the code to the new repo but understandably has some
> concerns about breaking changes but we are working together on
> refining the process to handle this.
>
> On Tue, May 17, 2022 at 5:22 PM LM <re...@gmail.com> wrote:
>
>> +1
>>
>> On Tue, May 17, 2022 at 1:35 PM QP Hou <qp...@neuralink.com> wrote:
>>
>> > +1 (binding)
>> >
>> > On Tue, May 17, 2022 at 1:27 PM David Li <li...@apache.org> wrote:
>> > >
>> > > +1 (binding)
>> > >
>> > > On Tue, May 17, 2022, at 16:00, Neal Richardson wrote:
>> > > > +1
>> > > >
>> > > > On Tue, May 17, 2022 at 12:46 PM Andrew Lamb
>> > > > <al...@influxdata.com>
>> > wrote:
>> > > >
>> > > >> +1 (binding)
>> > > >>
>> > > >> On Mon, May 16, 2022 at 9:56 AM Andy Grove
>> > > >> <an...@gmail.com>
>> > wrote:
>> > > >>
>> > > >> > I would like to propose that we move the Ballista project to
>> > > >> > a
>> new
>> > > >> > top-level *arrow-ballista* repository.
>> > > >> >
>> > > >> > The rationale for this (copied from the GitHub issue [1]) is:
>> > > >> >
>> > > >> > -
>> > > >> >
>> > > >> > Decouple release process for DataFusion and Ballista
>> > > >> > -
>> > > >> >
>> > > >> > Allow each project to have top-level documentation and
>> > > >> > user
>> > guides
>> > > >> that
>> > > >> > are targeting the appropriate audience
>> > > >> > -
>> > > >> >
>> > > >> > Reduce issue tracking and PR review burden for DataFusion
>> > maintainers
>> > > >> > who are not as interested in Ballista
>> > > >> > -
>> > > >> >
>> > > >> > Help avoid accidental circular dependencies being
>> > > >> > introduced
>> > between
>> > > >> the
>> > > >> > projects (such as [3])
>> > > >> > -
>> > > >> >
>> > > >> > Helps formalize the public API for DataFusion that other
>> > > >> > query
>> > engines
>> > > >> > should be using
>> > > >> >
>> > > >> > There is a design docment [3] that outlines the plan for
>> > implementing
>> > > >> this.
>> > > >> >
>> > > >> > Only votes from PMC members are binding, but all members of
>> > > >> > the
>> > community
>> > > >> > are encouraged to test the release and vote with "(non-binding)".
>> > The
>> > > >> vote
>> > > >> > will run for at least 72 hours.
>> > > >> >
>> > > >> > [ ] +1 Proceed with moving Ballista to a new arrow-ballista
>> > repository [
>> > > >> ]
>> > > >> > +0
>> > > >> >
>> > > >> > [ ] -1 Do not proceed with moving Ballista to a new
>> arrow-ballista
>> > > >> > repository because ...
>> > > >> >
>> > > >> > Here is my vote:
>> > > >> >
>> > > >> > +1 (binding)
>> > > >> >
>> > > >> > [1]
>> > > >> > https://nam12.safelinks.protection.outlook.com/?url=https%3A
>> > > >> > %2F%2Fgithub.com%2Fapache%2Farrow-datafusion%2Fissues%2F2502
>> > > >> > &data=05%7C01%7C%7C2a4c1255998b4cf101f908da39a462c6%7C84
>> > > >> > df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637885675437221022%
>> > > >> > 7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIi
>> > > >> > LCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=rQw
>> > > >> > 8n%2FkVW4nEq1bQ25IN%2FHmTQCu8zhyhnmg0XmJl0HE%3D&reserved
>> > > >> > =0
>> > > >> >
>> > > >> > [2]
>> > > >> > https://nam12.safelinks.protection.outlook.com/?url=https%3A
>> > > >> > %2F%2Fgithub.com%2Fapache%2Farrow-datafusion%2Fissues%2F2433
>> > > >> > &data=05%7C01%7C%7C2a4c1255998b4cf101f908da39a462c6%7C84
>> > > >> > df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637885675437221022%
>> > > >> > 7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIi
>> > > >> > LCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=TBU
>> > > >> > EG5Mrvn1SHFoa%2Fuu7Xee%2Fv8uiaOY4zXhR3ht0bEE%3D&reserved
>> > > >> > =0
>> > > >> >
>> > > >> > [3]
>> > > >> >
>> > > >> >
>> > > >>
>> >
>> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdoc
>> s.google.com%2Fdocument%2Fd%2F1jNRbadyStSrV5kifwn0khufAwq6OnzGczG4z8o
>> TQJP4%2Fedit%3Fusp%3Dsharing&data=05%7C01%7C%7C2a4c1255998b4cf101
>> f908da39a462c6%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637885675
>> 437221022%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzI
>> iLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=X2eZnNvPs4v
>> I40rytcT5vSmPQygl2qM%2F6dxyk3Ph6RA%3D&reserved=0
>> > > >> >
>> > > >>
>> >
>>
>
Re: [VOTE] [Rust] Move Ballista to new arrow-ballista repository
Posted by Andy Grove <an...@gmail.com>.
With 7 binding votes, and 3 non-binding votes, the vote passes. Thank you
to everyone who put the time into reading the proposal and voting on this
issue.
I will go ahead and create the new repo and will work with the DataFusion &
Ballista developers over the next couple weeks to implement this. I hope to
have this working smoothly before the next major release of DataFusion,
which we plan on releasing around one month from now.
Thanks,
Andy.
On Thu, May 19, 2022 at 8:28 AM Andy Grove <an...@gmail.com> wrote:
> Per Matthew's point about feedback from Ballista devs, I have been
> discussing this with yahoNanJing in the GitHub issue that was linked to in
> the start of this email thread and it seems they are comfortable with
> moving the code to the new repo but understandably has some concerns about
> breaking changes but we are working together on refining the process to
> handle this.
>
> On Tue, May 17, 2022 at 5:22 PM LM <re...@gmail.com> wrote:
>
>> +1
>>
>> On Tue, May 17, 2022 at 1:35 PM QP Hou <qp...@neuralink.com> wrote:
>>
>> > +1 (binding)
>> >
>> > On Tue, May 17, 2022 at 1:27 PM David Li <li...@apache.org> wrote:
>> > >
>> > > +1 (binding)
>> > >
>> > > On Tue, May 17, 2022, at 16:00, Neal Richardson wrote:
>> > > > +1
>> > > >
>> > > > On Tue, May 17, 2022 at 12:46 PM Andrew Lamb <al...@influxdata.com>
>> > wrote:
>> > > >
>> > > >> +1 (binding)
>> > > >>
>> > > >> On Mon, May 16, 2022 at 9:56 AM Andy Grove <an...@gmail.com>
>> > wrote:
>> > > >>
>> > > >> > I would like to propose that we move the Ballista project to a
>> new
>> > > >> > top-level *arrow-ballista* repository.
>> > > >> >
>> > > >> > The rationale for this (copied from the GitHub issue [1]) is:
>> > > >> >
>> > > >> > -
>> > > >> >
>> > > >> > Decouple release process for DataFusion and Ballista
>> > > >> > -
>> > > >> >
>> > > >> > Allow each project to have top-level documentation and user
>> > guides
>> > > >> that
>> > > >> > are targeting the appropriate audience
>> > > >> > -
>> > > >> >
>> > > >> > Reduce issue tracking and PR review burden for DataFusion
>> > maintainers
>> > > >> > who are not as interested in Ballista
>> > > >> > -
>> > > >> >
>> > > >> > Help avoid accidental circular dependencies being introduced
>> > between
>> > > >> the
>> > > >> > projects (such as [3])
>> > > >> > -
>> > > >> >
>> > > >> > Helps formalize the public API for DataFusion that other query
>> > engines
>> > > >> > should be using
>> > > >> >
>> > > >> > There is a design docment [3] that outlines the plan for
>> > implementing
>> > > >> this.
>> > > >> >
>> > > >> > Only votes from PMC members are binding, but all members of the
>> > community
>> > > >> > are encouraged to test the release and vote with "(non-binding)".
>> > The
>> > > >> vote
>> > > >> > will run for at least 72 hours.
>> > > >> >
>> > > >> > [ ] +1 Proceed with moving Ballista to a new arrow-ballista
>> > repository [
>> > > >> ]
>> > > >> > +0
>> > > >> >
>> > > >> > [ ] -1 Do not proceed with moving Ballista to a new
>> arrow-ballista
>> > > >> > repository because ...
>> > > >> >
>> > > >> > Here is my vote:
>> > > >> >
>> > > >> > +1 (binding)
>> > > >> >
>> > > >> > [1] https://github.com/apache/arrow-datafusion/issues/2502
>> > > >> >
>> > > >> > [2] https://github.com/apache/arrow-datafusion/issues/2433
>> > > >> >
>> > > >> > [3]
>> > > >> >
>> > > >> >
>> > > >>
>> >
>> https://docs.google.com/document/d/1jNRbadyStSrV5kifwn0khufAwq6OnzGczG4z8oTQJP4/edit?usp=sharing
>> > > >> >
>> > > >>
>> >
>>
>
Re: [VOTE] [Rust] Move Ballista to new arrow-ballista repository
Posted by Andy Grove <an...@gmail.com>.
Per Matthew's point about feedback from Ballista devs, I have been
discussing this with yahoNanJing in the GitHub issue that was linked to in
the start of this email thread and it seems they are comfortable with
moving the code to the new repo but understandably has some concerns about
breaking changes but we are working together on refining the process to
handle this.
On Tue, May 17, 2022 at 5:22 PM LM <re...@gmail.com> wrote:
> +1
>
> On Tue, May 17, 2022 at 1:35 PM QP Hou <qp...@neuralink.com> wrote:
>
> > +1 (binding)
> >
> > On Tue, May 17, 2022 at 1:27 PM David Li <li...@apache.org> wrote:
> > >
> > > +1 (binding)
> > >
> > > On Tue, May 17, 2022, at 16:00, Neal Richardson wrote:
> > > > +1
> > > >
> > > > On Tue, May 17, 2022 at 12:46 PM Andrew Lamb <al...@influxdata.com>
> > wrote:
> > > >
> > > >> +1 (binding)
> > > >>
> > > >> On Mon, May 16, 2022 at 9:56 AM Andy Grove <an...@gmail.com>
> > wrote:
> > > >>
> > > >> > I would like to propose that we move the Ballista project to a new
> > > >> > top-level *arrow-ballista* repository.
> > > >> >
> > > >> > The rationale for this (copied from the GitHub issue [1]) is:
> > > >> >
> > > >> > -
> > > >> >
> > > >> > Decouple release process for DataFusion and Ballista
> > > >> > -
> > > >> >
> > > >> > Allow each project to have top-level documentation and user
> > guides
> > > >> that
> > > >> > are targeting the appropriate audience
> > > >> > -
> > > >> >
> > > >> > Reduce issue tracking and PR review burden for DataFusion
> > maintainers
> > > >> > who are not as interested in Ballista
> > > >> > -
> > > >> >
> > > >> > Help avoid accidental circular dependencies being introduced
> > between
> > > >> the
> > > >> > projects (such as [3])
> > > >> > -
> > > >> >
> > > >> > Helps formalize the public API for DataFusion that other query
> > engines
> > > >> > should be using
> > > >> >
> > > >> > There is a design docment [3] that outlines the plan for
> > implementing
> > > >> this.
> > > >> >
> > > >> > Only votes from PMC members are binding, but all members of the
> > community
> > > >> > are encouraged to test the release and vote with "(non-binding)".
> > The
> > > >> vote
> > > >> > will run for at least 72 hours.
> > > >> >
> > > >> > [ ] +1 Proceed with moving Ballista to a new arrow-ballista
> > repository [
> > > >> ]
> > > >> > +0
> > > >> >
> > > >> > [ ] -1 Do not proceed with moving Ballista to a new arrow-ballista
> > > >> > repository because ...
> > > >> >
> > > >> > Here is my vote:
> > > >> >
> > > >> > +1 (binding)
> > > >> >
> > > >> > [1] https://github.com/apache/arrow-datafusion/issues/2502
> > > >> >
> > > >> > [2] https://github.com/apache/arrow-datafusion/issues/2433
> > > >> >
> > > >> > [3]
> > > >> >
> > > >> >
> > > >>
> >
> https://docs.google.com/document/d/1jNRbadyStSrV5kifwn0khufAwq6OnzGczG4z8oTQJP4/edit?usp=sharing
> > > >> >
> > > >>
> >
>
Re: [VOTE] [Rust] Move Ballista to new arrow-ballista repository
Posted by LM <re...@gmail.com>.
+1
On Tue, May 17, 2022 at 1:35 PM QP Hou <qp...@neuralink.com> wrote:
> +1 (binding)
>
> On Tue, May 17, 2022 at 1:27 PM David Li <li...@apache.org> wrote:
> >
> > +1 (binding)
> >
> > On Tue, May 17, 2022, at 16:00, Neal Richardson wrote:
> > > +1
> > >
> > > On Tue, May 17, 2022 at 12:46 PM Andrew Lamb <al...@influxdata.com>
> wrote:
> > >
> > >> +1 (binding)
> > >>
> > >> On Mon, May 16, 2022 at 9:56 AM Andy Grove <an...@gmail.com>
> wrote:
> > >>
> > >> > I would like to propose that we move the Ballista project to a new
> > >> > top-level *arrow-ballista* repository.
> > >> >
> > >> > The rationale for this (copied from the GitHub issue [1]) is:
> > >> >
> > >> > -
> > >> >
> > >> > Decouple release process for DataFusion and Ballista
> > >> > -
> > >> >
> > >> > Allow each project to have top-level documentation and user
> guides
> > >> that
> > >> > are targeting the appropriate audience
> > >> > -
> > >> >
> > >> > Reduce issue tracking and PR review burden for DataFusion
> maintainers
> > >> > who are not as interested in Ballista
> > >> > -
> > >> >
> > >> > Help avoid accidental circular dependencies being introduced
> between
> > >> the
> > >> > projects (such as [3])
> > >> > -
> > >> >
> > >> > Helps formalize the public API for DataFusion that other query
> engines
> > >> > should be using
> > >> >
> > >> > There is a design docment [3] that outlines the plan for
> implementing
> > >> this.
> > >> >
> > >> > Only votes from PMC members are binding, but all members of the
> community
> > >> > are encouraged to test the release and vote with "(non-binding)".
> The
> > >> vote
> > >> > will run for at least 72 hours.
> > >> >
> > >> > [ ] +1 Proceed with moving Ballista to a new arrow-ballista
> repository [
> > >> ]
> > >> > +0
> > >> >
> > >> > [ ] -1 Do not proceed with moving Ballista to a new arrow-ballista
> > >> > repository because ...
> > >> >
> > >> > Here is my vote:
> > >> >
> > >> > +1 (binding)
> > >> >
> > >> > [1] https://github.com/apache/arrow-datafusion/issues/2502
> > >> >
> > >> > [2] https://github.com/apache/arrow-datafusion/issues/2433
> > >> >
> > >> > [3]
> > >> >
> > >> >
> > >>
> https://docs.google.com/document/d/1jNRbadyStSrV5kifwn0khufAwq6OnzGczG4z8oTQJP4/edit?usp=sharing
> > >> >
> > >>
>
Re: [VOTE] [Rust] Move Ballista to new arrow-ballista repository
Posted by QP Hou <qp...@neuralink.com>.
+1 (binding)
On Tue, May 17, 2022 at 1:27 PM David Li <li...@apache.org> wrote:
>
> +1 (binding)
>
> On Tue, May 17, 2022, at 16:00, Neal Richardson wrote:
> > +1
> >
> > On Tue, May 17, 2022 at 12:46 PM Andrew Lamb <al...@influxdata.com> wrote:
> >
> >> +1 (binding)
> >>
> >> On Mon, May 16, 2022 at 9:56 AM Andy Grove <an...@gmail.com> wrote:
> >>
> >> > I would like to propose that we move the Ballista project to a new
> >> > top-level *arrow-ballista* repository.
> >> >
> >> > The rationale for this (copied from the GitHub issue [1]) is:
> >> >
> >> > -
> >> >
> >> > Decouple release process for DataFusion and Ballista
> >> > -
> >> >
> >> > Allow each project to have top-level documentation and user guides
> >> that
> >> > are targeting the appropriate audience
> >> > -
> >> >
> >> > Reduce issue tracking and PR review burden for DataFusion maintainers
> >> > who are not as interested in Ballista
> >> > -
> >> >
> >> > Help avoid accidental circular dependencies being introduced between
> >> the
> >> > projects (such as [3])
> >> > -
> >> >
> >> > Helps formalize the public API for DataFusion that other query engines
> >> > should be using
> >> >
> >> > There is a design docment [3] that outlines the plan for implementing
> >> this.
> >> >
> >> > Only votes from PMC members are binding, but all members of the community
> >> > are encouraged to test the release and vote with "(non-binding)". The
> >> vote
> >> > will run for at least 72 hours.
> >> >
> >> > [ ] +1 Proceed with moving Ballista to a new arrow-ballista repository [
> >> ]
> >> > +0
> >> >
> >> > [ ] -1 Do not proceed with moving Ballista to a new arrow-ballista
> >> > repository because ...
> >> >
> >> > Here is my vote:
> >> >
> >> > +1 (binding)
> >> >
> >> > [1] https://github.com/apache/arrow-datafusion/issues/2502
> >> >
> >> > [2] https://github.com/apache/arrow-datafusion/issues/2433
> >> >
> >> > [3]
> >> >
> >> >
> >> https://docs.google.com/document/d/1jNRbadyStSrV5kifwn0khufAwq6OnzGczG4z8oTQJP4/edit?usp=sharing
> >> >
> >>
Re: [VOTE] [Rust] Move Ballista to new arrow-ballista repository
Posted by David Li <li...@apache.org>.
+1 (binding)
On Tue, May 17, 2022, at 16:00, Neal Richardson wrote:
> +1
>
> On Tue, May 17, 2022 at 12:46 PM Andrew Lamb <al...@influxdata.com> wrote:
>
>> +1 (binding)
>>
>> On Mon, May 16, 2022 at 9:56 AM Andy Grove <an...@gmail.com> wrote:
>>
>> > I would like to propose that we move the Ballista project to a new
>> > top-level *arrow-ballista* repository.
>> >
>> > The rationale for this (copied from the GitHub issue [1]) is:
>> >
>> > -
>> >
>> > Decouple release process for DataFusion and Ballista
>> > -
>> >
>> > Allow each project to have top-level documentation and user guides
>> that
>> > are targeting the appropriate audience
>> > -
>> >
>> > Reduce issue tracking and PR review burden for DataFusion maintainers
>> > who are not as interested in Ballista
>> > -
>> >
>> > Help avoid accidental circular dependencies being introduced between
>> the
>> > projects (such as [3])
>> > -
>> >
>> > Helps formalize the public API for DataFusion that other query engines
>> > should be using
>> >
>> > There is a design docment [3] that outlines the plan for implementing
>> this.
>> >
>> > Only votes from PMC members are binding, but all members of the community
>> > are encouraged to test the release and vote with "(non-binding)". The
>> vote
>> > will run for at least 72 hours.
>> >
>> > [ ] +1 Proceed with moving Ballista to a new arrow-ballista repository [
>> ]
>> > +0
>> >
>> > [ ] -1 Do not proceed with moving Ballista to a new arrow-ballista
>> > repository because ...
>> >
>> > Here is my vote:
>> >
>> > +1 (binding)
>> >
>> > [1] https://github.com/apache/arrow-datafusion/issues/2502
>> >
>> > [2] https://github.com/apache/arrow-datafusion/issues/2433
>> >
>> > [3]
>> >
>> >
>> https://docs.google.com/document/d/1jNRbadyStSrV5kifwn0khufAwq6OnzGczG4z8oTQJP4/edit?usp=sharing
>> >
>>
Re: [VOTE] [Rust] Move Ballista to new arrow-ballista repository
Posted by Neal Richardson <ne...@gmail.com>.
+1
On Tue, May 17, 2022 at 12:46 PM Andrew Lamb <al...@influxdata.com> wrote:
> +1 (binding)
>
> On Mon, May 16, 2022 at 9:56 AM Andy Grove <an...@gmail.com> wrote:
>
> > I would like to propose that we move the Ballista project to a new
> > top-level *arrow-ballista* repository.
> >
> > The rationale for this (copied from the GitHub issue [1]) is:
> >
> > -
> >
> > Decouple release process for DataFusion and Ballista
> > -
> >
> > Allow each project to have top-level documentation and user guides
> that
> > are targeting the appropriate audience
> > -
> >
> > Reduce issue tracking and PR review burden for DataFusion maintainers
> > who are not as interested in Ballista
> > -
> >
> > Help avoid accidental circular dependencies being introduced between
> the
> > projects (such as [3])
> > -
> >
> > Helps formalize the public API for DataFusion that other query engines
> > should be using
> >
> > There is a design docment [3] that outlines the plan for implementing
> this.
> >
> > Only votes from PMC members are binding, but all members of the community
> > are encouraged to test the release and vote with "(non-binding)". The
> vote
> > will run for at least 72 hours.
> >
> > [ ] +1 Proceed with moving Ballista to a new arrow-ballista repository [
> ]
> > +0
> >
> > [ ] -1 Do not proceed with moving Ballista to a new arrow-ballista
> > repository because ...
> >
> > Here is my vote:
> >
> > +1 (binding)
> >
> > [1] https://github.com/apache/arrow-datafusion/issues/2502
> >
> > [2] https://github.com/apache/arrow-datafusion/issues/2433
> >
> > [3]
> >
> >
> https://docs.google.com/document/d/1jNRbadyStSrV5kifwn0khufAwq6OnzGczG4z8oTQJP4/edit?usp=sharing
> >
>
Re: [VOTE] [Rust] Move Ballista to new arrow-ballista repository
Posted by Andrew Lamb <al...@influxdata.com>.
+1 (binding)
On Mon, May 16, 2022 at 9:56 AM Andy Grove <an...@gmail.com> wrote:
> I would like to propose that we move the Ballista project to a new
> top-level *arrow-ballista* repository.
>
> The rationale for this (copied from the GitHub issue [1]) is:
>
> -
>
> Decouple release process for DataFusion and Ballista
> -
>
> Allow each project to have top-level documentation and user guides that
> are targeting the appropriate audience
> -
>
> Reduce issue tracking and PR review burden for DataFusion maintainers
> who are not as interested in Ballista
> -
>
> Help avoid accidental circular dependencies being introduced between the
> projects (such as [3])
> -
>
> Helps formalize the public API for DataFusion that other query engines
> should be using
>
> There is a design docment [3] that outlines the plan for implementing this.
>
> Only votes from PMC members are binding, but all members of the community
> are encouraged to test the release and vote with "(non-binding)". The vote
> will run for at least 72 hours.
>
> [ ] +1 Proceed with moving Ballista to a new arrow-ballista repository [ ]
> +0
>
> [ ] -1 Do not proceed with moving Ballista to a new arrow-ballista
> repository because ...
>
> Here is my vote:
>
> +1 (binding)
>
> [1] https://github.com/apache/arrow-datafusion/issues/2502
>
> [2] https://github.com/apache/arrow-datafusion/issues/2433
>
> [3]
>
> https://docs.google.com/document/d/1jNRbadyStSrV5kifwn0khufAwq6OnzGczG4z8oTQJP4/edit?usp=sharing
>
RE: [VOTE] [Rust] Move Ballista to new arrow-ballista repository
Posted by Matthew Turner <ma...@outlook.com>.
In general I am +1 on this.
However, I believe there is a team who has been actively working on many Ballista enhancements and I don't think that I have seen feedback from them on this yet (I apologize if I missed it). I would be interested in getting their view - in particular on making sure ballista keeps up with datafusion.
-----Original Message-----
From: Andy Grove <an...@gmail.com>
Sent: Monday, May 16, 2022 9:55 AM
To: dev <de...@arrow.apache.org>
Subject: [VOTE] [Rust] Move Ballista to new arrow-ballista repository
I would like to propose that we move the Ballista project to a new top-level *arrow-ballista* repository.
The rationale for this (copied from the GitHub issue [1]) is:
-
Decouple release process for DataFusion and Ballista
-
Allow each project to have top-level documentation and user guides that
are targeting the appropriate audience
-
Reduce issue tracking and PR review burden for DataFusion maintainers
who are not as interested in Ballista
-
Help avoid accidental circular dependencies being introduced between the
projects (such as [3])
-
Helps formalize the public API for DataFusion that other query engines
should be using
There is a design docment [3] that outlines the plan for implementing this.
Only votes from PMC members are binding, but all members of the community are encouraged to test the release and vote with "(non-binding)". The vote will run for at least 72 hours.
[ ] +1 Proceed with moving Ballista to a new arrow-ballista repository [ ]
+0
[ ] -1 Do not proceed with moving Ballista to a new arrow-ballista repository because ...
Here is my vote:
+1 (binding)
[1] https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Farrow-datafusion%2Fissues%2F2502&data=05%7C01%7C%7C6d6114e6344942d5890308da3743b571%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637883061195430782%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=46cU4UZ85eXCnbP6krI9DEWjI74%2FHqMphcHbNbTP%2F%2Fc%3D&reserved=0
[2] https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Farrow-datafusion%2Fissues%2F2433&data=05%7C01%7C%7C6d6114e6344942d5890308da3743b571%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637883061195430782%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=p7W55b5VhezFRi3ETQFJ3pntTIttMPX8C0D8aMLLcSw%3D&reserved=0
[3]
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.google.com%2Fdocument%2Fd%2F1jNRbadyStSrV5kifwn0khufAwq6OnzGczG4z8oTQJP4%2Fedit%3Fusp%3Dsharing&data=05%7C01%7C%7C6d6114e6344942d5890308da3743b571%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637883061195430782%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=tNRaj0SwE60RLEMqhe3auQnw0dBTBA13EhUwBM5XFEg%3D&reserved=0
Re: [VOTE] [Rust] Move Ballista to new arrow-ballista repository
Posted by Micah Kornfield <em...@gmail.com>.
+1 (binding)
On Tue, May 17, 2022 at 10:05 AM Wes McKinney <we...@gmail.com> wrote:
> +1 (binding)
>
> On Tue, May 17, 2022 at 4:10 AM vin jake <ja...@gmail.com> wrote:
> >
> > +1, It's reasonable
> >
> > On Mon, May 16, 2022 at 9:56 PM Andy Grove <an...@gmail.com>
> wrote:
> >
> > > I would like to propose that we move the Ballista project to a new
> > > top-level *arrow-ballista* repository.
> > >
> > > The rationale for this (copied from the GitHub issue [1]) is:
> > >
> > > -
> > >
> > > Decouple release process for DataFusion and Ballista
> > > -
> > >
> > > Allow each project to have top-level documentation and user guides
> that
> > > are targeting the appropriate audience
> > > -
> > >
> > > Reduce issue tracking and PR review burden for DataFusion
> maintainers
> > > who are not as interested in Ballista
> > > -
> > >
> > > Help avoid accidental circular dependencies being introduced
> between the
> > > projects (such as [3])
> > > -
> > >
> > > Helps formalize the public API for DataFusion that other query
> engines
> > > should be using
> > >
> > > There is a design docment [3] that outlines the plan for implementing
> this.
> > >
> > > Only votes from PMC members are binding, but all members of the
> community
> > > are encouraged to test the release and vote with "(non-binding)". The
> vote
> > > will run for at least 72 hours.
> > >
> > > [ ] +1 Proceed with moving Ballista to a new arrow-ballista repository
> [ ]
> > > +0
> > >
> > > [ ] -1 Do not proceed with moving Ballista to a new arrow-ballista
> > > repository because ...
> > >
> > > Here is my vote:
> > >
> > > +1 (binding)
> > >
> > > [1] https://github.com/apache/arrow-datafusion/issues/2502
> > >
> > > [2] https://github.com/apache/arrow-datafusion/issues/2433
> > >
> > > [3]
> > >
> > >
> https://docs.google.com/document/d/1jNRbadyStSrV5kifwn0khufAwq6OnzGczG4z8oTQJP4/edit?usp=sharing
> > >
>
Re: [VOTE] [Rust] Move Ballista to new arrow-ballista repository
Posted by Wes McKinney <we...@gmail.com>.
+1 (binding)
On Tue, May 17, 2022 at 4:10 AM vin jake <ja...@gmail.com> wrote:
>
> +1, It's reasonable
>
> On Mon, May 16, 2022 at 9:56 PM Andy Grove <an...@gmail.com> wrote:
>
> > I would like to propose that we move the Ballista project to a new
> > top-level *arrow-ballista* repository.
> >
> > The rationale for this (copied from the GitHub issue [1]) is:
> >
> > -
> >
> > Decouple release process for DataFusion and Ballista
> > -
> >
> > Allow each project to have top-level documentation and user guides that
> > are targeting the appropriate audience
> > -
> >
> > Reduce issue tracking and PR review burden for DataFusion maintainers
> > who are not as interested in Ballista
> > -
> >
> > Help avoid accidental circular dependencies being introduced between the
> > projects (such as [3])
> > -
> >
> > Helps formalize the public API for DataFusion that other query engines
> > should be using
> >
> > There is a design docment [3] that outlines the plan for implementing this.
> >
> > Only votes from PMC members are binding, but all members of the community
> > are encouraged to test the release and vote with "(non-binding)". The vote
> > will run for at least 72 hours.
> >
> > [ ] +1 Proceed with moving Ballista to a new arrow-ballista repository [ ]
> > +0
> >
> > [ ] -1 Do not proceed with moving Ballista to a new arrow-ballista
> > repository because ...
> >
> > Here is my vote:
> >
> > +1 (binding)
> >
> > [1] https://github.com/apache/arrow-datafusion/issues/2502
> >
> > [2] https://github.com/apache/arrow-datafusion/issues/2433
> >
> > [3]
> >
> > https://docs.google.com/document/d/1jNRbadyStSrV5kifwn0khufAwq6OnzGczG4z8oTQJP4/edit?usp=sharing
> >
Re: [VOTE] [Rust] Move Ballista to new arrow-ballista repository
Posted by vin jake <ja...@gmail.com>.
+1, It's reasonable
On Mon, May 16, 2022 at 9:56 PM Andy Grove <an...@gmail.com> wrote:
> I would like to propose that we move the Ballista project to a new
> top-level *arrow-ballista* repository.
>
> The rationale for this (copied from the GitHub issue [1]) is:
>
> -
>
> Decouple release process for DataFusion and Ballista
> -
>
> Allow each project to have top-level documentation and user guides that
> are targeting the appropriate audience
> -
>
> Reduce issue tracking and PR review burden for DataFusion maintainers
> who are not as interested in Ballista
> -
>
> Help avoid accidental circular dependencies being introduced between the
> projects (such as [3])
> -
>
> Helps formalize the public API for DataFusion that other query engines
> should be using
>
> There is a design docment [3] that outlines the plan for implementing this.
>
> Only votes from PMC members are binding, but all members of the community
> are encouraged to test the release and vote with "(non-binding)". The vote
> will run for at least 72 hours.
>
> [ ] +1 Proceed with moving Ballista to a new arrow-ballista repository [ ]
> +0
>
> [ ] -1 Do not proceed with moving Ballista to a new arrow-ballista
> repository because ...
>
> Here is my vote:
>
> +1 (binding)
>
> [1] https://github.com/apache/arrow-datafusion/issues/2502
>
> [2] https://github.com/apache/arrow-datafusion/issues/2433
>
> [3]
>
> https://docs.google.com/document/d/1jNRbadyStSrV5kifwn0khufAwq6OnzGczG4z8oTQJP4/edit?usp=sharing
>