[DISCUSS] Annual rotation of Arrow PMC chair

[Wes McKinney]

hello all,

As we discussed at the end of 2020 [1], we would like to have a
roughly annual rotation of the Apache Arrow PMC chair. The
responsibilities of the PMC chair are mainly bureaucratic: the
submission of quarterly board reports on reporter.apache.org and
managing the PMC roster on whimsy.apache.org. The PMC chair is also
responsible for making sure issues are raised with the board if
needed.

I would nominate Kouhei Sutou to be the next chair if he is willing.

Thanks all,
Wes

[1]: https://lists.apache.org/thread/mvsnj0zqf33wztcl2pvryq3rf0l3s57y

[ANNOUNCE] New Arrow PMC member: Yibo Cai

[Wes McKinney]

The Project Management Committee (PMC) for Apache Arrow has invited
Yibo Cai to become a PMC member and we are pleased to announce
that Yibo has accepted.

Congratulations and welcome!

Re: [ANNOUNCE] New Arrow PMC member: Yibo Cai

[Antoine Pitrou]

Welcome on board Yibo!


Le 04/01/2022 à 09:51, Wes McKinney a écrit :

The Project Management Committee (PMC) for Apache Arrow has invited
Yibo Cai to become a PMC member and we are pleased to announce
that Yibo has accepted.

Congratulations and welcome!

Re: [ANNOUNCE] New Arrow PMC member: Yibo Cai

[Eduardo Ponce]

Congratulations Yibo! Thanks for all your contributions and guidance.

On Tue, Jan 4, 2022 at 3:52 AM Wes McKinney  wrote:

> The Project Management Committee (PMC) for Apache Arrow has invited
> Yibo Cai to become a PMC member and we are pleased to announce
> that Yibo has accepted.
>
> Congratulations and welcome!
>

Re: Preparing for version 7.0.0 release

[Antoine Pitrou]

Le 03/01/2022 à 15:44, Alessandro Molina a écrit :

The plan seems to be to cut a release the 2nd or 3rd week of January, a new
confluence page was made to track progress of the release (
https://cwiki.apache.org/confluence/display/ARROW/Arrow+7.0.0+Release ).

It would greatly help in the process of preparing for the release if you
could review tickets that are assigned to you in the "TODO Backlog" and
move those that you think you will not be able to close in ~1 week to
"Version 8.0.0" in Jira, so that we can start preparing release
announcements etc with a good estimate of what's actually going to end up
in the release.


Note there's also the cpp-7.0.0 version on the Parquet JIRA:
https://issues.apache.org/jira/projects/PARQUET/versions/12350844

Regards

Antoine.

Re: [VOTE] Release Apache Arrow JS 6.0.2

[Wes McKinney]

hi Dominik -- I just wanted to confirm that you're going to wait for
the 7.0.0 release? We should still try to get things set up so that JS
patch source releases can be made easily.

On Fri, Dec 10, 2021 at 4:39 PM Tim Paine  wrote:
>
> Just wanted to note that our move from Arrow JS to Wasm arrow resulted in a 
> pretty substantial speedup, although we solve none of the problems of 
> exposing wasm arrow over JS since we use it directly from C++.
>
> Initial PR: https://github.com/finos/perspective/pull/755 
> 
> Standalone Arrow C++ to wasm via emscripten: 
> https://github.com/timkpaine/arrow-wasm-cpp 
> 
> (Note that neither utilize all of arrow, just a carve out of IPC stuff)
>
>
>
>
> Tim Paine
> tim.paine.nyc
> 908.721.1185
>
> > On Dec 9, 2021, at 14:18, Dominik Moritz  wrote:
> >
> >>
> >> Arrow rust implementation is in another repository and has support for
> >>
> > Javascript/Webassembly :
> >>
> >> https://github.com/apache/arrow-rs/tree/master/arrow
> >>
> >> The release cadence for the Rust implementation is much higher than for
> >> the  C++ implementation. Efficiencies might be gained by releasing Rust
> >> and Javascript point implementations together since then the process of
> >> creating and verifying signed software would minimize PMC workload.Arrow
> >> rust implementation is in another repository and has support for
> >>
> > Javascript/Webassembly :
> >>
> >> https://github.com/apache/arrow-rs/tree/master/arrow
> >>
> >> The release cadence for the Rust implementation is much higher than for
> >> the  C++ implementation. Efficiencies might be gained by releasing Rust
> >> and Javascript point implementations together since then the process of
> >> creating and verifying signed software would minimize PMC workload.
> >
> >
> > The biggest challenge with making a web-library for Arrow with WASM is a
> > performant JS API. I think realistically, we will have a pure JS Arrow
> > library for a few years. Do you think we could sync the release processes
> > even if Arrow JS is not in the rust repo? If so, I would love to learn more
> > about how that process would work.
> >
> > On Dec 7, 2021 at 03:43:13, Benson Muite  wrote:
> >
> >> At the moment, the release is not packaged or signed. Thus one can only
> >> run the tests on the branch in the git repository. A script to do that
> >> on Linux is available at:
> >>
> >> https://github.com/bkmgit/arrow/blob/ARROW-14801/dev/release/verify-js.sh
> >>
> >> My understanding is that only PMC members can sign, at the moment not
> >> many seem to use Javascript extensively. Can create a script for
> >> generating the Javascript only release source package based on the
> >> current source packaging and release scripts, but a PMC member would
> >> need to have this signed and uploaded.
> >>
> >> @Dominik - was not aware of arrow-wasm, thanks.
> >>
> >> Arrow rust implementation is in another repository and has support for
> >> Javascript/Webassembly :
> >>
> >> https://github.com/apache/arrow-rs/tree/master/arrow
> >>
> >> The release cadence for the Rust implementation is much higher than for
> >> the  C++ implementation. Efficiencies might be gained by releasing Rust
> >> and Javascript point implementations together since then the process of
> >> creating and verifying signed software would minimize PMC workload.
> >>
> >> Benson
> >>
> >> On 12/6/21 1:01 AM, Wes McKinney wrote:
> >>
> >> hi Dominik — can you provide instructions for how we should verify the
> >>
> >> release, aside from checking the GPG signature and checksums?
> >>
> >>
> >> On Sun, Nov 28, 2021 at 12:41 PM Dominik Moritz 
> >> wrote:
> >>
> >>>
> >>
> >>> Are you talking about https://github.com/domoritz/arrow-wasm? It
> >> definitely
> >>
> >>> isn’t ready for prime time. The overhead of WASM, some issues with the
> >> Rust
> >>
> >>> implementation (some of which I think will be addressed with the Arrow2
> >>
> >>> Rust migration), and the much larger bundle size make it not practical
> >>
> >>> right now. As the WASM ecosystem matures, we can reevaluate and maybe
> >> also
> >>
> >>> consider moving only some of the processing in WASM and leave the rest in
> >>
> >>> JS. I’m pretty excited about WASM and what it could bring to Arrow
> >>
> >>> especially when combined with WebGPU.
> >>
> >>>
> >>
> >>> Either way, I think we should release the 6.0.2 version soon. @PMC, could
> >>
> >>> you vote on the patch release?
> >>
> >>>
> >>
> >>> On Nov 28, 2021 at 04:33:41, Benson Muite 
> >>
> >>> wrote:
> >>
> >>>
> >>
>  Rust implementation can be compiled to WebAssembly and is released
> >>
>  biweekly. The Javascript version compiled from Rust may not satisfy all
> >>
>  Javascript users, but maybe there could be some collaboration to reduce
> >>
>  duplicated efforts?
> >>
> 
> >>
> 
> >>
>  On 11/23/21 9:52 PM, Dominik Moritz wrote:
> >>
> 
> >>
> 

Re: [ANNOUNCE] New Arrow PMC member: Yibo Cai

[Rok Mihevc]

Congratulations Yibo!

On Tue, Jan 4, 2022 at 9:54 AM Eduardo Ponce  wrote:
>
> Congratulations Yibo! Thanks for all your contributions and guidance.
>
> On Tue, Jan 4, 2022 at 3:52 AM Wes McKinney  wrote:
>
> > The Project Management Committee (PMC) for Apache Arrow has invited
> > Yibo Cai to become a PMC member and we are pleased to announce
> > that Yibo has accepted.
> >
> > Congratulations and welcome!
> >

Re: [ANNOUNCE] New Arrow PMC member: Yibo Cai

[Jacky Lee]

Congratulations Yibo!

Rok Mihevc  于2022年1月4日周二 20:07写道：

> Congratulations Yibo!
>
> On Tue, Jan 4, 2022 at 9:54 AM Eduardo Ponce  wrote:
> >
> > Congratulations Yibo! Thanks for all your contributions and guidance.
> >
> > On Tue, Jan 4, 2022 at 3:52 AM Wes McKinney  wrote:
> >
> > > The Project Management Committee (PMC) for Apache Arrow has invited
> > > Yibo Cai to become a PMC member and we are pleased to announce
> > > that Yibo has accepted.
> > >
> > > Congratulations and welcome!
> > >
>

Re: [ANNOUNCE] New Arrow PMC member: Yibo Cai

[Neal Richardson]

Congratulations, Yibo!

Neal

On Tue, Jan 4, 2022 at 7:15 AM Jacky Lee  wrote:

> Congratulations Yibo!
>
> Rok Mihevc  于2022年1月4日周二 20:07写道：
>
> > Congratulations Yibo!
> >
> > On Tue, Jan 4, 2022 at 9:54 AM Eduardo Ponce 
> wrote:
> > >
> > > Congratulations Yibo! Thanks for all your contributions and guidance.
> > >
> > > On Tue, Jan 4, 2022 at 3:52 AM Wes McKinney 
> wrote:
> > >
> > > > The Project Management Committee (PMC) for Apache Arrow has invited
> > > > Yibo Cai to become a PMC member and we are pleased to announce
> > > > that Yibo has accepted.
> > > >
> > > > Congratulations and welcome!
> > > >
> >
>

Re: [ANNOUNCE] New Arrow PMC member: Yibo Cai

[Andrew Lamb]

Congratulations, Yibo!

Andrew

On Tue, Jan 4, 2022 at 8:14 AM Neal Richardson 
wrote:

> Congratulations, Yibo!
>
> Neal
>
> On Tue, Jan 4, 2022 at 7:15 AM Jacky Lee  wrote:
>
> > Congratulations Yibo!
> >
> > Rok Mihevc  于2022年1月4日周二 20:07写道：
> >
> > > Congratulations Yibo!
> > >
> > > On Tue, Jan 4, 2022 at 9:54 AM Eduardo Ponce 
> > wrote:
> > > >
> > > > Congratulations Yibo! Thanks for all your contributions and guidance.
> > > >
> > > > On Tue, Jan 4, 2022 at 3:52 AM Wes McKinney 
> > wrote:
> > > >
> > > > > The Project Management Committee (PMC) for Apache Arrow has invited
> > > > > Yibo Cai to become a PMC member and we are pleased to announce
> > > > > that Yibo has accepted.
> > > > >
> > > > > Congratulations and welcome!
> > > > >
> > >
> >
>

Re: Preparing for version 7.0.0 release

[Alessandro Molina]

Quick note that all "Unassigned" issues that were not already started have
been moved to 8.0.0.
End of next week I'll do another pass and move all "Improvements/New
Features" that are not yet started to 8.0.0

On Tue, Jan 4, 2022 at 10:02 AM Antoine Pitrou  wrote:

>
> Le 03/01/2022 à 15:44, Alessandro Molina a écrit :
> > The plan seems to be to cut a release the 2nd or 3rd week of January, a
> new
> > confluence page was made to track progress of the release (
> > https://cwiki.apache.org/confluence/display/ARROW/Arrow+7.0.0+Release ).
> >
> > It would greatly help in the process of preparing for the release if you
> > could review tickets that are assigned to you in the "TODO Backlog" and
> > move those that you think you will not be able to close in ~1 week to
> > "Version 8.0.0" in Jira, so that we can start preparing release
> > announcements etc with a good estimate of what's actually going to end up
> > in the release.
>
> Note there's also the cpp-7.0.0 version on the Parquet JIRA:
> https://issues.apache.org/jira/projects/PARQUET/versions/12350844
>
> Regards
>
> Antoine.
>

Re: [VOTE] Release Apache Arrow JS 6.0.2

[Dominik Moritz]

 Hi Wes,

Thanks for the follow up and I’m sorry for not following up myself. Yes, we
will publish the fixes in the Arrow 7 release.

I’ll keep it in my backlog to figure out how to make patch releases. Over
the break, I added more testing for bundlers so we can hopefully reduce the
need for patch releases for JS and ship more robust bundles.

Best wishes,
Dominik

On Jan 4, 2022 at 06:13:19, Wes McKinney  wrote:

> hi Dominik -- I just wanted to confirm that you're going to wait for
> the 7.0.0 release? We should still try to get things set up so that JS
> patch source releases can be made easily.
>
> On Fri, Dec 10, 2021 at 4:39 PM Tim Paine  wrote:
>
>
> Just wanted to note that our move from Arrow JS to Wasm arrow resulted in
> a pretty substantial speedup, although we solve none of the problems of
> exposing wasm arrow over JS since we use it directly from C++.
>
>
> Initial PR: https://github.com/finos/perspective/pull/755 <
> https://github.com/finos/perspective/pull/755>
>
> Standalone Arrow C++ to wasm via emscripten:
> https://github.com/timkpaine/arrow-wasm-cpp <
> https://github.com/timkpaine/arrow-wasm-cpp>
>
> (Note that neither utilize all of arrow, just a carve out of IPC stuff)
>
>
>
>
>
> Tim Paine
>
> tim.paine.nyc
>
> 908.721.1185
>
>
> > On Dec 9, 2021, at 14:18, Dominik Moritz  wrote:
>
> >
>
> >>
>
> >> Arrow rust implementation is in another repository and has support for
>
> >>
>
> > Javascript/Webassembly :
>
> >>
>
> >> https://github.com/apache/arrow-rs/tree/master/arrow
>
> >>
>
> >> The release cadence for the Rust implementation is much higher than for
>
> >> the  C++ implementation. Efficiencies might be gained by releasing Rust
>
> >> and Javascript point implementations together since then the process of
>
> >> creating and verifying signed software would minimize PMC workload.Arrow
>
> >> rust implementation is in another repository and has support for
>
> >>
>
> > Javascript/Webassembly :
>
> >>
>
> >> https://github.com/apache/arrow-rs/tree/master/arrow
>
> >>
>
> >> The release cadence for the Rust implementation is much higher than for
>
> >> the  C++ implementation. Efficiencies might be gained by releasing Rust
>
> >> and Javascript point implementations together since then the process of
>
> >> creating and verifying signed software would minimize PMC workload.
>
> >
>
> >
>
> > The biggest challenge with making a web-library for Arrow with WASM is a
>
> > performant JS API. I think realistically, we will have a pure JS Arrow
>
> > library for a few years. Do you think we could sync the release processes
>
> > even if Arrow JS is not in the rust repo? If so, I would love to learn
> more
>
> > about how that process would work.
>
> >
>
> > On Dec 7, 2021 at 03:43:13, Benson Muite 
> wrote:
>
> >
>
> >> At the moment, the release is not packaged or signed. Thus one can only
>
> >> run the tests on the branch in the git repository. A script to do that
>
> >> on Linux is available at:
>
> >>
>
> >>
> https://github.com/bkmgit/arrow/blob/ARROW-14801/dev/release/verify-js.sh
>
> >>
>
> >> My understanding is that only PMC members can sign, at the moment not
>
> >> many seem to use Javascript extensively. Can create a script for
>
> >> generating the Javascript only release source package based on the
>
> >> current source packaging and release scripts, but a PMC member would
>
> >> need to have this signed and uploaded.
>
> >>
>
> >> @Dominik - was not aware of arrow-wasm, thanks.
>
> >>
>
> >> Arrow rust implementation is in another repository and has support for
>
> >> Javascript/Webassembly :
>
> >>
>
> >> https://github.com/apache/arrow-rs/tree/master/arrow
>
> >>
>
> >> The release cadence for the Rust implementation is much higher than for
>
> >> the  C++ implementation. Efficiencies might be gained by releasing Rust
>
> >> and Javascript point implementations together since then the process of
>
> >> creating and verifying signed software would minimize PMC workload.
>
> >>
>
> >> Benson
>
> >>
>
> >> On 12/6/21 1:01 AM, Wes McKinney wrote:
>
> >>
>
> >> hi Dominik — can you provide instructions for how we should verify the
>
> >>
>
> >> release, aside from checking the GPG signature and checksums?
>
> >>
>
> >>
>
> >> On Sun, Nov 28, 2021 at 12:41 PM Dominik Moritz 
>
> >> wrote:
>
> >>
>
> >>>
>
> >>
>
> >>> Are you talking about https://github.com/domoritz/arrow-wasm? It
>
> >> definitely
>
> >>
>
> >>> isn’t ready for prime time. The overhead of WASM, some issues with the
>
> >> Rust
>
> >>
>
> >>> implementation (some of which I think will be addressed with the Arrow2
>
> >>
>
> >>> Rust migration), and the much larger bundle size make it not practical
>
> >>
>
> >>> right now. As the WASM ecosystem matures, we can reevaluate and maybe
>
> >> also
>
> >>
>
> >>> consider moving only some of the processing in WASM and leave the rest
> in
>
> >>
>
> >>> JS. I’m pretty excited about WASM and what it could bring to Arrow
>
> >>
>
> >>> especially when combined wi

Re: [ANNOUNCE] New Arrow PMC member: Yibo Cai

[Wang Xudong]

Congratulations！

xudong

Andrew Lamb  于2022年1月4日周二 21:43写道：

> Congratulations, Yibo!
>
> Andrew
>
> On Tue, Jan 4, 2022 at 8:14 AM Neal Richardson <
> neal.p.richard...@gmail.com>
> wrote:
>
> > Congratulations, Yibo!
> >
> > Neal
> >
> > On Tue, Jan 4, 2022 at 7:15 AM Jacky Lee  wrote:
> >
> > > Congratulations Yibo!
> > >
> > > Rok Mihevc  于2022年1月4日周二 20:07写道：
> > >
> > > > Congratulations Yibo!
> > > >
> > > > On Tue, Jan 4, 2022 at 9:54 AM Eduardo Ponce 
> > > wrote:
> > > > >
> > > > > Congratulations Yibo! Thanks for all your contributions and
> guidance.
> > > > >
> > > > > On Tue, Jan 4, 2022 at 3:52 AM Wes McKinney 
> > > wrote:
> > > > >
> > > > > > The Project Management Committee (PMC) for Apache Arrow has
> invited
> > > > > > Yibo Cai to become a PMC member and we are pleased to announce
> > > > > > that Yibo has accepted.
> > > > > >
> > > > > > Congratulations and welcome!
> > > > > >
> > > >
> > >
> >
>

Re: [ANNOUNCE] New Arrow PMC member: Yibo Cai

[Niranda Perera]

Congrats Yibo! :-)

On Tue, Jan 4, 2022 at 10:00 AM Wang Xudong  wrote:

> Congratulations！
>
> xudong
>
> Andrew Lamb  于2022年1月4日周二 21:43写道：
>
> > Congratulations, Yibo!
> >
> > Andrew
> >
> > On Tue, Jan 4, 2022 at 8:14 AM Neal Richardson <
> > neal.p.richard...@gmail.com>
> > wrote:
> >
> > > Congratulations, Yibo!
> > >
> > > Neal
> > >
> > > On Tue, Jan 4, 2022 at 7:15 AM Jacky Lee  wrote:
> > >
> > > > Congratulations Yibo!
> > > >
> > > > Rok Mihevc  于2022年1月4日周二 20:07写道：
> > > >
> > > > > Congratulations Yibo!
> > > > >
> > > > > On Tue, Jan 4, 2022 at 9:54 AM Eduardo Ponce 
> > > > wrote:
> > > > > >
> > > > > > Congratulations Yibo! Thanks for all your contributions and
> > guidance.
> > > > > >
> > > > > > On Tue, Jan 4, 2022 at 3:52 AM Wes McKinney  >
> > > > wrote:
> > > > > >
> > > > > > > The Project Management Committee (PMC) for Apache Arrow has
> > invited
> > > > > > > Yibo Cai to become a PMC member and we are pleased to announce
> > > > > > > that Yibo has accepted.
> > > > > > >
> > > > > > > Congratulations and welcome!
> > > > > > >
> > > > >
> > > >
> > >
> >
>


-- 
Niranda Perera
https://niranda.dev/
@n1r44 

Re: [ANNOUNCE] New Arrow PMC member: Yibo Cai

[Benson Muite]

Congratulations!

On 1/4/22 6:00 PM, Wang Xudong wrote:

Congratulations！

xudong

Andrew Lamb  于2022年1月4日周二 21:43写道：


Congratulations, Yibo!

Andrew

On Tue, Jan 4, 2022 at 8:14 AM Neal Richardson <
neal.p.richard...@gmail.com>
wrote:


Congratulations, Yibo!

Neal

On Tue, Jan 4, 2022 at 7:15 AM Jacky Lee  wrote:


Congratulations Yibo!

Rok Mihevc  于2022年1月4日周二 20:07写道：


Congratulations Yibo!

On Tue, Jan 4, 2022 at 9:54 AM Eduardo Ponce 

wrote:


Congratulations Yibo! Thanks for all your contributions and

guidance.


On Tue, Jan 4, 2022 at 3:52 AM Wes McKinney 

wrote:



The Project Management Committee (PMC) for Apache Arrow has

invited

Yibo Cai to become a PMC member and we are pleased to announce
that Yibo has accepted.

Congratulations and welcome!

Re: [ANNOUNCE] New Arrow PMC member: Yibo Cai

[David Li]

Congrats, Yibo!

-David

On Tue, Jan 4, 2022, at 10:09, Benson Muite wrote:
> Congratulations!
> 
> On 1/4/22 6:00 PM, Wang Xudong wrote:
> > Congratulations！
> > 
> > xudong
> > 
> > Andrew Lamb  于2022年1月4日周二 21:43写道：
> > 
> >> Congratulations, Yibo!
> >>
> >> Andrew
> >>
> >> On Tue, Jan 4, 2022 at 8:14 AM Neal Richardson <
> >> neal.p.richard...@gmail.com>
> >> wrote:
> >>
> >>> Congratulations, Yibo!
> >>>
> >>> Neal
> >>>
> >>> On Tue, Jan 4, 2022 at 7:15 AM Jacky Lee  wrote:
> >>>
>  Congratulations Yibo!
> 
>  Rok Mihevc  于2022年1月4日周二 20:07写道：
> 
> > Congratulations Yibo!
> >
> > On Tue, Jan 4, 2022 at 9:54 AM Eduardo Ponce 
>  wrote:
> >>
> >> Congratulations Yibo! Thanks for all your contributions and
> >> guidance.
> >>
> >> On Tue, Jan 4, 2022 at 3:52 AM Wes McKinney 
>  wrote:
> >>
> >>> The Project Management Committee (PMC) for Apache Arrow has
> >> invited
> >>> Yibo Cai to become a PMC member and we are pleased to announce
> >>> that Yibo has accepted.
> >>>
> >>> Congratulations and welcome!
> >>>
> >
> 
> >>>
> >>
> > 
> 
> 

Re: [ANNOUNCE] New Arrow PMC member: Yibo Cai

[Weston Pace]

Congratulations Yibo!

On Tue, Jan 4, 2022, 5:14 AM David Li  wrote:

> Congrats, Yibo!
>
> -David
>
> On Tue, Jan 4, 2022, at 10:09, Benson Muite wrote:
> > Congratulations!
> >
> > On 1/4/22 6:00 PM, Wang Xudong wrote:
> > > Congratulations！
> > >
> > > xudong
> > >
> > > Andrew Lamb  于2022年1月4日周二 21:43写道：
> > >
> > >> Congratulations, Yibo!
> > >>
> > >> Andrew
> > >>
> > >> On Tue, Jan 4, 2022 at 8:14 AM Neal Richardson <
> > >> neal.p.richard...@gmail.com>
> > >> wrote:
> > >>
> > >>> Congratulations, Yibo!
> > >>>
> > >>> Neal
> > >>>
> > >>> On Tue, Jan 4, 2022 at 7:15 AM Jacky Lee  wrote:
> > >>>
> >  Congratulations Yibo!
> > 
> >  Rok Mihevc  于2022年1月4日周二 20:07写道：
> > 
> > > Congratulations Yibo!
> > >
> > > On Tue, Jan 4, 2022 at 9:54 AM Eduardo Ponce 
> >  wrote:
> > >>
> > >> Congratulations Yibo! Thanks for all your contributions and
> > >> guidance.
> > >>
> > >> On Tue, Jan 4, 2022 at 3:52 AM Wes McKinney 
> >  wrote:
> > >>
> > >>> The Project Management Committee (PMC) for Apache Arrow has
> > >> invited
> > >>> Yibo Cai to become a PMC member and we are pleased to announce
> > >>> that Yibo has accepted.
> > >>>
> > >>> Congratulations and welcome!
> > >>>
> > >
> > 
> > >>>
> > >>
> > >
> >
> >

Re: [ANNOUNCE] New Arrow PMC member: Yibo Cai

[Ian Joiner]

Congrats Yibo!

Ian

On Tuesday, January 4, 2022, Weston Pace  wrote:

> Congratulations Yibo!
>
> On Tue, Jan 4, 2022, 5:14 AM David Li  wrote:
>
> > Congrats, Yibo!
> >
> > -David
> >
> > On Tue, Jan 4, 2022, at 10:09, Benson Muite wrote:
> > > Congratulations!
> > >
> > > On 1/4/22 6:00 PM, Wang Xudong wrote:
> > > > Congratulations！
> > > >
> > > > xudong
> > > >
> > > > Andrew Lamb  于2022年1月4日周二 21:43写道：
> > > >
> > > >> Congratulations, Yibo!
> > > >>
> > > >> Andrew
> > > >>
> > > >> On Tue, Jan 4, 2022 at 8:14 AM Neal Richardson <
> > > >> neal.p.richard...@gmail.com>
> > > >> wrote:
> > > >>
> > > >>> Congratulations, Yibo!
> > > >>>
> > > >>> Neal
> > > >>>
> > > >>> On Tue, Jan 4, 2022 at 7:15 AM Jacky Lee 
> wrote:
> > > >>>
> > >  Congratulations Yibo!
> > > 
> > >  Rok Mihevc  于2022年1月4日周二 20:07写道：
> > > 
> > > > Congratulations Yibo!
> > > >
> > > > On Tue, Jan 4, 2022 at 9:54 AM Eduardo Ponce <
> edponc...@gmail.com>
> > >  wrote:
> > > >>
> > > >> Congratulations Yibo! Thanks for all your contributions and
> > > >> guidance.
> > > >>
> > > >> On Tue, Jan 4, 2022 at 3:52 AM Wes McKinney <
> wesmck...@gmail.com>
> > >  wrote:
> > > >>
> > > >>> The Project Management Committee (PMC) for Apache Arrow has
> > > >> invited
> > > >>> Yibo Cai to become a PMC member and we are pleased to announce
> > > >>> that Yibo has accepted.
> > > >>>
> > > >>> Congratulations and welcome!
> > > >>>
> > > >
> > > 
> > > >>>
> > > >>
> > > >
> > >
> > >
>

Re: [RESULT][VOTE] Proposed addition to Arrow Flight: Arrow Flight RPC

[James Duong]

If I recall correctly, there was interest in providing a blog post to
accompany the announcement of Flight SQL's release. Where should this be
submitted and what other steps would be needed for this?

On Sat, Dec 25, 2021 at 8:07 PM Jacques Nadeau  wrote:

> That's great news. Congrats and thanks to the team who worked on it. This
> is a great addition to Arrow!
>
> On Thu, Dec 23, 2021, 11:26 AM David Li  wrote:
>
> > The integration tests and existing PRs were merged into a separate
> branch.
> > We also merged in a few build fixes during final review. Just in time for
> > the holidays, Flight SQL has now been merged into the main branch, thanks
> > again to everyone who participated!
> >
> > I will begin reviewing the additional proposals next.
> >
> > -David
> >
> > On Fri, Dec 17, 2021, at 17:07, James Duong wrote:
> > > Yes, additional metadata would just be using the Field metadata map.
> The
> > > protocol is the same, we have just pre-defined keys for some fields
> that
> > > would be used for JDBC column attributes.
> > >
> > > Our preference would be that we get the currently approved protocol
> > merged
> > > into master first (after completing the integration tests) and then
> have
> > a
> > > separate vote on the TypeInfo changes. There's significant value in
> > adding
> > > Flight-SQL already and it'd be great to make that available. It's
> natural
> > > that there will be an ongoing need to add extensions to the protocol as
> > it
> > > gets used in more scenarios. Now that we have a solid foundation, we
> can
> > > examine further changes on a case-by-case basis.
> > >
> > > On Thu, Dec 16, 2021 at 2:42 PM David Li  wrote:
> > >
> > > > Strictly speaking we should have a vote since it is updating the
> format
> > > > definition files we already voted on.
> > > >
> > > > I am curious about what exactly you mean by additional column
> metadata,
> > > > but if it's just going to be encoded into the key-value metadata
> then I
> > > > don't see a problem there. (As in: it sounds like it fits in the
> Field
> > > > class given it's encoded in the Field metadata!)
> > > >
> > > > -David
> > > >
> > > > On Thu, Dec 16, 2021, at 16:14, James Duong wrote:
> > > > > Hi David,
> > > > >
> > > > > While working on the JDBC driver on top of Flight SQL and on
> > integration
> > > > > tests, we identified a couple of enhancements that were needed.
> > > > > 1. The ability to report data type information, as done in this PR:
> > > > > https://github.com/apache/arrow/pull/11982. This PR adds another
> RPC
> > > > > request for this information.
> > > > > 2. Additional column metadata that's outside of the Schema/Field
> > classes
> > > > in
> > > > > Arrow (PR pending) when returning Arrow schemas. The planned PR
> uses
> > the
> > > > > Arrow Field's MetadataMap to encode extra metadata rather than
> > altering
> > > > any
> > > > > protobuf definitions.
> > > > >
> > > > > Should these additional changes go in together with the rest of
> > > > Flight-SQL,
> > > > > or be approved separately?
> > > > >
> > > > > On Thu, Dec 16, 2021 at 7:54 AM Kyle Porter <
> ky...@bitquilltech.com
> > > > .invalid>
> > > > > wrote:
> > > > >
> > > > > > Thanks All - we'll look to get the tests merged into this branch
> > so we
> > > > can
> > > > > > close ASAP.
> > > > > >
> > > > > > *Kyle Porter*
> > > > > > CEO
> > > > > > Bit Quill Technologies Inc.
> > > > > > Office: +1.778.331.3355 | Direct: +1.604.441.7318 |
> > > > ky...@bitquilltech.com
> > > > > > https://www.bitquill.com
> > > > > >
> > > > > > This email message is for the sole use of the intended
> recipient(s)
> > > > and may
> > > > > > contain confidential and privileged information.  Any
> unauthorized
> > > > review,
> > > > > > use, disclosure, or distribution is prohibited.  If you are not
> the
> > > > > > intended recipient, please contact the sender by reply email and
> > > > destroy
> > > > > > all copies of the original message.  Thank you.
> > > > > >
> > > > > >
> > > > > > On Wed, Dec 15, 2021 at 9:11 AM David Li 
> > wrote:
> > > > > >
> > > > > > > My vote: +1
> > > > > > >
> > > > > > > The vote passes with three +1 (binding) votes, one +1 (non
> > binding)
> > > > vote,
> > > > > > > and one -0.5 (binding) vote.
> > > > > > >
> > > > > > > However, we will first merge into a separate branch and
> implement
> > > > > > > integration tests before merging into the main branch. JIRA for
> > > > > > integration
> > > > > > > tests: https://issues.apache.org/jira/browse/ARROW-15112
> > > > > > >
> > > > > > > @Kyle I've created the branch flight-sql[1], would you prefer I
> > > > merge in
> > > > > > > your existing PRs, or would you prefer to create new PRs
> against
> > that
> > > > > > > branch (given you've already started on things)?
> > > > > > >
> > > > > > > On a side note - do we document the requirements for proposed
> > > > additions
> > > > > > > somewhere? (multiple implementations, integration tests) It
> > would be
> > > > nic

Re: [RESULT][VOTE] Proposed addition to Arrow Flight: Arrow Flight RPC

[David Li]

Hey James - thanks for the reminder, sorry for dropping the ball here.

I think you can submit a PR to arrow-site: https://github.com/apache/arrow-site 
and we can iterate/review it from there.

Thanks,
David

On Tue, Jan 4, 2022, at 12:25, James Duong wrote:
> If I recall correctly, there was interest in providing a blog post to
> accompany the announcement of Flight SQL's release. Where should this be
> submitted and what other steps would be needed for this?
> 
> On Sat, Dec 25, 2021 at 8:07 PM Jacques Nadeau  wrote:
> 
> > That's great news. Congrats and thanks to the team who worked on it. This
> > is a great addition to Arrow!
> >
> > On Thu, Dec 23, 2021, 11:26 AM David Li  wrote:
> >
> > > The integration tests and existing PRs were merged into a separate
> > branch.
> > > We also merged in a few build fixes during final review. Just in time for
> > > the holidays, Flight SQL has now been merged into the main branch, thanks
> > > again to everyone who participated!
> > >
> > > I will begin reviewing the additional proposals next.
> > >
> > > -David
> > >
> > > On Fri, Dec 17, 2021, at 17:07, James Duong wrote:
> > > > Yes, additional metadata would just be using the Field metadata map.
> > The
> > > > protocol is the same, we have just pre-defined keys for some fields
> > that
> > > > would be used for JDBC column attributes.
> > > >
> > > > Our preference would be that we get the currently approved protocol
> > > merged
> > > > into master first (after completing the integration tests) and then
> > have
> > > a
> > > > separate vote on the TypeInfo changes. There's significant value in
> > > adding
> > > > Flight-SQL already and it'd be great to make that available. It's
> > natural
> > > > that there will be an ongoing need to add extensions to the protocol as
> > > it
> > > > gets used in more scenarios. Now that we have a solid foundation, we
> > can
> > > > examine further changes on a case-by-case basis.
> > > >
> > > > On Thu, Dec 16, 2021 at 2:42 PM David Li  wrote:
> > > >
> > > > > Strictly speaking we should have a vote since it is updating the
> > format
> > > > > definition files we already voted on.
> > > > >
> > > > > I am curious about what exactly you mean by additional column
> > metadata,
> > > > > but if it's just going to be encoded into the key-value metadata
> > then I
> > > > > don't see a problem there. (As in: it sounds like it fits in the
> > Field
> > > > > class given it's encoded in the Field metadata!)
> > > > >
> > > > > -David
> > > > >
> > > > > On Thu, Dec 16, 2021, at 16:14, James Duong wrote:
> > > > > > Hi David,
> > > > > >
> > > > > > While working on the JDBC driver on top of Flight SQL and on
> > > integration
> > > > > > tests, we identified a couple of enhancements that were needed.
> > > > > > 1. The ability to report data type information, as done in this PR:
> > > > > > https://github.com/apache/arrow/pull/11982. This PR adds another
> > RPC
> > > > > > request for this information.
> > > > > > 2. Additional column metadata that's outside of the Schema/Field
> > > classes
> > > > > in
> > > > > > Arrow (PR pending) when returning Arrow schemas. The planned PR
> > uses
> > > the
> > > > > > Arrow Field's MetadataMap to encode extra metadata rather than
> > > altering
> > > > > any
> > > > > > protobuf definitions.
> > > > > >
> > > > > > Should these additional changes go in together with the rest of
> > > > > Flight-SQL,
> > > > > > or be approved separately?
> > > > > >
> > > > > > On Thu, Dec 16, 2021 at 7:54 AM Kyle Porter <
> > ky...@bitquilltech.com
> > > > > .invalid>
> > > > > > wrote:
> > > > > >
> > > > > > > Thanks All - we'll look to get the tests merged into this branch
> > > so we
> > > > > can
> > > > > > > close ASAP.
> > > > > > >
> > > > > > > *Kyle Porter*
> > > > > > > CEO
> > > > > > > Bit Quill Technologies Inc.
> > > > > > > Office: +1.778.331.3355 | Direct: +1.604.441.7318 |
> > > > > ky...@bitquilltech.com
> > > > > > > https://www.bitquill.com
> > > > > > >
> > > > > > > This email message is for the sole use of the intended
> > recipient(s)
> > > > > and may
> > > > > > > contain confidential and privileged information.  Any
> > unauthorized
> > > > > review,
> > > > > > > use, disclosure, or distribution is prohibited.  If you are not
> > the
> > > > > > > intended recipient, please contact the sender by reply email and
> > > > > destroy
> > > > > > > all copies of the original message.  Thank you.
> > > > > > >
> > > > > > >
> > > > > > > On Wed, Dec 15, 2021 at 9:11 AM David Li 
> > > wrote:
> > > > > > >
> > > > > > > > My vote: +1
> > > > > > > >
> > > > > > > > The vote passes with three +1 (binding) votes, one +1 (non
> > > binding)
> > > > > vote,
> > > > > > > > and one -0.5 (binding) vote.
> > > > > > > >
> > > > > > > > However, we will first merge into a separate branch and
> > implement
> > > > > > > > integration tests before merging into the main branch. JIRA for
> > > > > > > integration
> > > > > > > > tests: 

Re: [DataFusion] Question about Accumulator API and maybe potential bugs

[LM]

Hi Jorge,

That makes sense, thanks for the clarification.

Thanks,
Lin

On Mon, 3 Jan 2022 at 23:49, Jorge Cardoso Leitão 
wrote:

> Hi,
>
> The accumulator API is designed to accept multiple columns (e.g. the
> pearson correlation takes 2 columns, not one). &values[0] corresponds to
> the first column passed to the accumulator. All concrete implementations of
> accumulators in DataFusion atm only accept one column (Sum, Avg, Count,
> Min, Max), but the API is designed to accept with multiple columns.
>
> So, update_batch(&mut self, values: &[ArrayRef]) corresponds to: update the
> accumulator from n columns. For sum, this would be 1, for pearson
> correlation this would be 2, for e.g. a ML model whose weights are computed
> over all columns, this would be the number of input columns N of the model.
> For stddev, you should use 1, since stddev is a function of a single
> column.
>
> `update(&mut self, values: &[ScalarValue])` corresponds to updating the
> state with intermediary states. In a HashAggregate, we reduce each
> partition, and use `update` to compute the final value from the
> intermediary (scalar) states.
>
> Hope this helps,
> Jorge
>
>
>
> On Tue, Jan 4, 2022 at 5:55 AM LM  wrote:
>
> > Hi All,
> >
> > I just started looking into DataFusion and am considering using it as the
> > platform for our next gen analytics solution. To get started, I tried to
> > add a few functions such as stddev. While writing the code I noticed some
> > discrepancies (it may also be my unfamiliarity of the code base) in the
> > Accumulator API and the implementation of some functions. The API is
> > defined as the following:
> >
> > pub trait Accumulator: Send + Sync + Debug {
> > /// Returns the state of the accumulator at the end of the accumulation.
> > // in the case of an average on which we track `sum` and `n`, this
> function
> > should return a vector
> > // of two values, sum and n.
> > fn state(&self) -> Result>;
> >
> > /// updates the accumulator's state from a vector of scalars.
> > fn update(&mut self, values: &[ScalarValue]) -> Result<()>;
> >
> > /// updates the accumulator's state from a vector of arrays.
> > fn update_batch(&mut self, values: &[ArrayRef]) -> Result<()> {
> > if values.is_empty() {
> > return Ok(());
> > };
> > (0..values[0].len()).try_for_each(|index| {
> > let v = values
> > .iter()
> > .map(|array| ScalarValue::try_from_array(array, index))
> > .collect::>>()?;
> > self.update(&v)
> > })
> > I am only quoting the update and update_batch functions for brevity, same
> > for the merge functions. So here it indicates that the update function
> > takes a *vector* and update_batch takes *vector of array. *
> >
> > When reading code for some actual implementation for example *sum* and
> > *average,
> > *both implementations assume when update is called *only one *value is
> > passed in; and when update_batch is called *only one *array is passed in.
> >
> > impl Accumulator for AvgAccumulator {
> > fn state(&self) -> Result> {
> > Ok(vec![ScalarValue::from(self.count), self.sum.clone()])
> > }
> >
> > fn update(&mut self, values: &[ScalarValue]) -> Result<()> {
> > let values = &values[0];
> >
> > self.count += (!values.is_null()) as u64;
> > self.sum = sum::sum(&self.sum, values)?;
> >
> > Ok(())
> > }
> >
> > fn update_batch(&mut self, values: &[ArrayRef]) -> Result<()> {
> > let values = &values[0];
> >
> > self.count += (values.len() - values.data().null_count()) as u64;
> > self.sum = sum::sum(&self.sum, &sum::sum_batch(values)?)?;
> > Ok(())
> >
> > impl Accumulator for SumAccumulator {
> > fn state(&self) -> Result> {
> > Ok(vec![self.sum.clone()])
> > }
> >
> > fn update(&mut self, values: &[ScalarValue]) -> Result<()> {
> > // sum(v1, v2, v3) = v1 + v2 + v3
> > self.sum = sum(&self.sum, &values[0])?;
> > Ok(())
> > }
> >
> > fn update_batch(&mut self, values: &[ArrayRef]) -> Result<()> {
> > let values = &values[0];
> > self.sum = sum(&self.sum, &sum_batch(values)?)?;
> > Ok(())
> > }
> >
> > Could someone shed some light in case I missed anything?
> >
> > Regards,
> > Lin
> >
>

Re: [DISCUSS] Annual rotation of Arrow PMC chair

[Jacques Nadeau]

Hey Wes, thanks for bringing this up. And more importantly, thanks for
working as the PMC chair this last year!

I think Kouhei would be a great choice for the PMC chair.

Jacques

On Tue, Jan 4, 2022 at 12:44 AM Wes McKinney  wrote:

> hello all,
>
> As we discussed at the end of 2020 [1], we would like to have a
> roughly annual rotation of the Apache Arrow PMC chair. The
> responsibilities of the PMC chair are mainly bureaucratic: the
> submission of quarterly board reports on reporter.apache.org and
> managing the PMC roster on whimsy.apache.org. The PMC chair is also
> responsible for making sure issues are raised with the board if
> needed.
>
> I would nominate Kouhei Sutou to be the next chair if he is willing.
>
> Thanks all,
> Wes
>
> [1]: https://lists.apache.org/thread/mvsnj0zqf33wztcl2pvryq3rf0l3s57y
>

Re: [DISCUSS] [RUST] More Frequent arrow-rs release schedule

[Andrew Lamb]

> Are there parts of the library that are more stable?

It is hard to tell -- for example I would have said the "parquet" API is
basically stable (as it hasn't been changed significantly) but there is
some non trivial work afoot to improve its performance which will result in
breaking changes

> I don't know that the lockstep versioning between Rust and C++ is buying
us anything.

I agree with this -- I think it is what @Jorge Cardoso Leitão
 predicted during some past discussions related
to arrow2.


On Mon, Jan 3, 2022 at 10:18 AM Weston Pace  wrote:

> Are there parts of the library that are more stable?  For example, in
> the C++ API the "parquet" namespace is stable and shouldn't encounter
> much breaking change but the "compute" namespace is marked
> "experimental" (in documentation) and much more liable for breaking
> change.  If there were a way to mark particular parts of the API as
> "experimental" then I think these parts could have breaking changes as
> part of a minor release.  This obeys the semver rules because your
> experimental APIs are not part of your "public API".
>
> That being said, I'm just backseat driving at this point, so feel free
> to discard the thought.  I don't know that the lockstep versioning
> between Rust and C++ is buying us anything.  I think it is more
> meaningful for something like R/C++ where the former is just bindings
> upon the latter.  There is no guarantee that version X of C++ and
> version X of Rust share any common features or compatibility.
>
> -Weston
>
> On Mon, Jan 3, 2022 at 2:23 AM Andrew Lamb  wrote:
> >
> > I think Micah and Adam have hit on the core issue -- there are
> inconsistent
> > meanings ascribed to versions numbers "1.0.0" and "stable"
> >
> > Specifically, I think everyone agrees
> > * "1.0.0"+ means "stable"
> > * Some software clearly is unstable (APIs change all the time, couldn't
> be
> > use by other software)
> > * Some software is clearly stable (public API never changes)
> >
> > However, there are many packages that fall between the two extremes
> > (arrow-rs and most of the rust ecosystem in my opinion): that change but
> > are "stable enough" to be used in other projects.
> >
> > I don't really care about the value of the version. What I care about are
> > 1. predictable regular releases and
> > 2. allowing the APIs to evolve over time without causing undue stress on
> > users (e.g that their CI jobs start failing without them changing
> anything)
> >
> > Andrew
>

Re: [DISCUSS] [RUST] More Frequent arrow-rs release schedule

[Andrew Lamb]

In conclusion, from my perspective maintaining an active release branch
with stable patches and major releases every 3 months doesn't provide
enough value for the cost

The cost is borne both by me actually creating the releases as well as
users who are slowed down picking up updates for dependent libraries (the
latest version of tonic, for example).

Unless there is significant pushback (ideally along with a volunteer to
help maintain a stable branch) I will plan to start doing releases for
arrow-rs directly from master as proposed on [1] , starting with arrow-rs
7.0 (will make a candidate later this week and hope to release early next)

Thank you,
Andrew

[1]: https://github.com/apache/arrow-rs/issues/1120

On Tue, Jan 4, 2022 at 4:32 PM Andrew Lamb  wrote:

> > Are there parts of the library that are more stable?
>
> It is hard to tell -- for example I would have said the "parquet" API is
> basically stable (as it hasn't been changed significantly) but there is
> some non trivial work afoot to improve its performance which will result in
> breaking changes
>
> > I don't know that the lockstep versioning between Rust and C++ is buying
> us anything.
>
> I agree with this -- I think it is what @Jorge Cardoso Leitão
>  predicted during some past discussions related
> to arrow2.
>
>
> On Mon, Jan 3, 2022 at 10:18 AM Weston Pace  wrote:
>
>> Are there parts of the library that are more stable?  For example, in
>> the C++ API the "parquet" namespace is stable and shouldn't encounter
>> much breaking change but the "compute" namespace is marked
>> "experimental" (in documentation) and much more liable for breaking
>> change.  If there were a way to mark particular parts of the API as
>> "experimental" then I think these parts could have breaking changes as
>> part of a minor release.  This obeys the semver rules because your
>> experimental APIs are not part of your "public API".
>>
>> That being said, I'm just backseat driving at this point, so feel free
>> to discard the thought.  I don't know that the lockstep versioning
>> between Rust and C++ is buying us anything.  I think it is more
>> meaningful for something like R/C++ where the former is just bindings
>> upon the latter.  There is no guarantee that version X of C++ and
>> version X of Rust share any common features or compatibility.
>>
>> -Weston
>>
>> On Mon, Jan 3, 2022 at 2:23 AM Andrew Lamb  wrote:
>> >
>> > I think Micah and Adam have hit on the core issue -- there are
>> inconsistent
>> > meanings ascribed to versions numbers "1.0.0" and "stable"
>> >
>> > Specifically, I think everyone agrees
>> > * "1.0.0"+ means "stable"
>> > * Some software clearly is unstable (APIs change all the time, couldn't
>> be
>> > use by other software)
>> > * Some software is clearly stable (public API never changes)
>> >
>> > However, there are many packages that fall between the two extremes
>> > (arrow-rs and most of the rust ecosystem in my opinion): that change but
>> > are "stable enough" to be used in other projects.
>> >
>> > I don't really care about the value of the version. What I care about
>> are
>> > 1. predictable regular releases and
>> > 2. allowing the APIs to evolve over time without causing undue stress on
>> > users (e.g that their CI jobs start failing without them changing
>> anything)
>> >
>> > Andrew
>>
>

Re: [DISCUSS] Annual rotation of Arrow PMC chair

[Andrew Lamb]

I second that -- thank you Wes for doing the process that keeps Arrow
churning along.

I also believe Kouhei would be a great choice for the PMC chair.

Andrew

On Tue, Jan 4, 2022 at 2:27 PM Jacques Nadeau  wrote:

> Hey Wes, thanks for bringing this up. And more importantly, thanks for
> working as the PMC chair this last year!
>
> I think Kouhei would be a great choice for the PMC chair.
>
> Jacques
>
> On Tue, Jan 4, 2022 at 12:44 AM Wes McKinney  wrote:
>
> > hello all,
> >
> > As we discussed at the end of 2020 [1], we would like to have a
> > roughly annual rotation of the Apache Arrow PMC chair. The
> > responsibilities of the PMC chair are mainly bureaucratic: the
> > submission of quarterly board reports on reporter.apache.org and
> > managing the PMC roster on whimsy.apache.org. The PMC chair is also
> > responsible for making sure issues are raised with the board if
> > needed.
> >
> > I would nominate Kouhei Sutou to be the next chair if he is willing.
> >
> > Thanks all,
> > Wes
> >
> > [1]: https://lists.apache.org/thread/mvsnj0zqf33wztcl2pvryq3rf0l3s57y
> >
>

Re: [RESULT] Release Apache Arrow Rust 6.5.0 RC1

[Andrew Lamb]

Update here is that the author doesn't want to yank the crate with the
incorrect version information. Given we are so close to a 7.0.0 release
anyways (will make one later this week) I am not going to pursue it further
and focus my efforts on that next release

Sorry about that for anyone waiting for 6.5.0



On Wed, Dec 29, 2021 at 6:56 AM Andrew Lamb  wrote:

> With four +1 votes (3 binding, a non binding) the release is approved
>
> The release is available here:
>   https://dist.apache.org/repos/dist/release/arrow/arrow-rs-6.5.0
>
> It has also been uploaded to crates.io:
> https://crates.io/crates/arrow/6.5.0
> https://crates.io/crates/parquet/6.5.0
> https://crates.io/crates/parquet-derive/6.5.0
>
> NOTE there is an issue uploading arrow-flight 6.5.0 due to a bug [1] that
> was released in another crate and how arrow-flight pins versions.
>
> We are working with the author of that crate to yank the bad version so we
> can publish the arrow-flight 6.5.0 crate [2]. However if the author does
> not do so, we may have to create and vote on a 6.5.1 version to get this
> out.
>
> [1] https://github.com/apache/arrow-rs/issues/1101
> [2] https://github.com/dtolnay/quote/issues/204
>
>
> On Tue, Dec 28, 2021 at 6:33 AM Jorge Cardoso Leitão <
> jorgecarlei...@gmail.com> wrote:
>
> > +1
> >
> > Thanks,
> > Jorge
> >
> >
> > On Fri, Dec 24, 2021 at 3:21 AM Wang Xudong 
> > wrote:
> >
> > > +1 (non-binding)
> > >
> > > Happy holidays
> > >
> > > ---
> > > xudong
> > >
> > > Andy Grove  于2021年12月24日周五 09:19写道：
> > >
> > > > +1 (binding)
> > > >
> > > > Thanks,
> > > >
> > > > Andy.
> > > >
> > > > On Thu, Dec 23, 2021 at 2:26 PM Andrew Lamb 
> > > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > Happy holidays to those of you who are celebrating. I would like to
> > > > propose
> > > > > a release of Apache Arrow Rust Implementation, version 6.5.0.
> > > > >
> > > > > This release candidate is based on commit:
> > > > > 70069c62f03b74d5e05ec75b808086edeefeecaf [1]
> > > > >
> > > > > The proposed release tarball and signatures are hosted at [2].
> > > > >
> > > > > The changelog is located at [3].
> > > > >
> > > > > Please download, verify checksums and signatures, run the unit
> tests,
> > > > > and vote on the release. There is a script [4] that automates some
> of
> > > > > the verification.
> > > > >
> > > > > The vote will be open for at least 72 hours.
> > > > >
> > > > > [ ] +1 Release this as Apache Arrow Rust
> > > > > [ ] +0
> > > > > [ ] -1 Do not release this as Apache Arrow Rust  because...
> > > > >
> > > > > [1]:
> > > > >
> > > > >
> > > >
> > >
> >
> https://github.com/apache/arrow-rs/tree/70069c62f03b74d5e05ec75b808086edeefeecaf
> > > > > [2]:
> > > > >
> > https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-rs-6.5.0-rc1
> > > > > [3]:
> > > > >
> > > > >
> > > >
> > >
> >
> https://github.com/apache/arrow-rs/blob/70069c62f03b74d5e05ec75b808086edeefeecaf/CHANGELOG.md
> > > > > [4]:
> > > > >
> > > > >
> > > >
> > >
> >
> https://github.com/apache/arrow-rs/blob/master/dev/release/verify-release-candidate.sh
> > > > > -
> > > > > Running rat license checker on
> > > > >
> > > > >
> > > >
> > >
> >
> /Users/alamb/Software/arrow-rs/dev/dist/apache-arrow-rs-6.5.0-rc1/apache-arrow-rs-6.5.0.tar.gz
> > > > >
> > > >
> > >
> >
>

Re: [DISCUSS] Annual rotation of Arrow PMC chair

[Neal Richardson]

+1 one to all of that. I enthusiastically endorse Kou, if he's interested!

Neal

On Tue, Jan 4, 2022 at 4:40 PM Andrew Lamb  wrote:

> I second that -- thank you Wes for doing the process that keeps Arrow
> churning along.
>
> I also believe Kouhei would be a great choice for the PMC chair.
>
> Andrew
>
> On Tue, Jan 4, 2022 at 2:27 PM Jacques Nadeau  wrote:
>
> > Hey Wes, thanks for bringing this up. And more importantly, thanks for
> > working as the PMC chair this last year!
> >
> > I think Kouhei would be a great choice for the PMC chair.
> >
> > Jacques
> >
> > On Tue, Jan 4, 2022 at 12:44 AM Wes McKinney 
> wrote:
> >
> > > hello all,
> > >
> > > As we discussed at the end of 2020 [1], we would like to have a
> > > roughly annual rotation of the Apache Arrow PMC chair. The
> > > responsibilities of the PMC chair are mainly bureaucratic: the
> > > submission of quarterly board reports on reporter.apache.org and
> > > managing the PMC roster on whimsy.apache.org. The PMC chair is also
> > > responsible for making sure issues are raised with the board if
> > > needed.
> > >
> > > I would nominate Kouhei Sutou to be the next chair if he is willing.
> > >
> > > Thanks all,
> > > Wes
> > >
> > > [1]: https://lists.apache.org/thread/mvsnj0zqf33wztcl2pvryq3rf0l3s57y
> > >
> >
>

Re: [DISCUSS] Annual rotation of Arrow PMC chair

[Mauricio Vargas]

I disappeared here in September, but yes +1

On Tue, Jan 4, 2022 at 7:45 PM Neal Richardson 
wrote:

> +1 one to all of that. I enthusiastically endorse Kou, if he's interested!
>
> Neal
>
> On Tue, Jan 4, 2022 at 4:40 PM Andrew Lamb  wrote:
>
> > I second that -- thank you Wes for doing the process that keeps Arrow
> > churning along.
> >
> > I also believe Kouhei would be a great choice for the PMC chair.
> >
> > Andrew
> >
> > On Tue, Jan 4, 2022 at 2:27 PM Jacques Nadeau 
> wrote:
> >
> > > Hey Wes, thanks for bringing this up. And more importantly, thanks for
> > > working as the PMC chair this last year!
> > >
> > > I think Kouhei would be a great choice for the PMC chair.
> > >
> > > Jacques
> > >
> > > On Tue, Jan 4, 2022 at 12:44 AM Wes McKinney 
> > wrote:
> > >
> > > > hello all,
> > > >
> > > > As we discussed at the end of 2020 [1], we would like to have a
> > > > roughly annual rotation of the Apache Arrow PMC chair. The
> > > > responsibilities of the PMC chair are mainly bureaucratic: the
> > > > submission of quarterly board reports on reporter.apache.org and
> > > > managing the PMC roster on whimsy.apache.org. The PMC chair is also
> > > > responsible for making sure issues are raised with the board if
> > > > needed.
> > > >
> > > > I would nominate Kouhei Sutou to be the next chair if he is willing.
> > > >
> > > > Thanks all,
> > > > Wes
> > > >
> > > > [1]:
> https://lists.apache.org/thread/mvsnj0zqf33wztcl2pvryq3rf0l3s57y
> > > >
> > >
> >
>


-- 
—
*Mauricio 'Pachá' Vargas Sepúlveda*
Site: pacha.dev
Blog: pacha.dev/blog