Re: [VOTE] Move issue tracking to GitHub Issues
+1 (binding) but let's make sure we have a quality migration to keep as much of the JIRA metadata as possible. Regards Antoine. Le 27/10/2022 à 01:02, Neal Richardson a écrit : I propose that we move issue tracking from the ASF's Jira to GitHub Issues. This has been discussed on [1] and [2] and there seems to be consensus. A number of Arrow subprojects already use GitHub Issues; this moves the issue tracking for `apache/arrow` into GitHub along with the source code. The vote will be open for at least 72 hours. [ ] +1 Leave ASF Jira and move to GitHub Issues [ ] +0 [ ] -1 Remain in Jira because... My vote: +1 Neal [1]: https://lists.apache.org/thread/l545m95xmf3w47oxwqxvg811or7b93tb [2]: https://lists.apache.org/thread/0vwj8gdo55jly5zn16wksrotyqqm0zqr
[Discuss][Python] Stop publishing universal wheels?
Hello, Currently, for macOS we're publishing both arm64, x86_64 *and* universal2 binary wheels (the latter contain both arm64 and x86_64 code in a single binary). Here are some observations from me: * Producing universal2 wheels is more complex than producing single-architecture wheels (we actually have to build for both architectures separately, then merge the results); it's also one more CI/packaging configuration to look after * x86-64 Macs are legacy and are gradually disappearing (especially for high-performance applications where ARM Macs are massively faster) * Numpy publishes only architecture-specific wheels, while Pandas publishes both architecture-specific and universal wheels * Size-wise, a universal wheel is not much smaller than the sum of architecture-specific wheels (for example, 43.7 MB for pyarrow-9.0.0-cp310-cp310, vs. 24.0 MB + 21.6 MB) Is there any reason why we should continue publishing universal wheels for macOS? Regards Antoine.
Re: [VOTE] Move issue tracking to GitHub Issues
+1 (non-binding) Rok On Thu, Oct 27, 2022 at 9:19 AM Antoine Pitrou wrote: > > +1 (binding) but let's make sure we have a quality migration to keep as > much of the JIRA metadata as possible. > > Regards > > Antoine. > > > Le 27/10/2022 à 01:02, Neal Richardson a écrit : > > I propose that we move issue tracking from the ASF's Jira to GitHub > Issues. > > This has been discussed on [1] and [2] and there seems to be consensus. A > > number of Arrow subprojects already use GitHub Issues; this moves the > issue > > tracking for `apache/arrow` into GitHub along with the source code. > > > > The vote will be open for at least 72 hours. > > > > [ ] +1 Leave ASF Jira and move to GitHub Issues > > [ ] +0 > > [ ] -1 Remain in Jira because... > > > > My vote: +1 > > > > Neal > > > > > > [1]: https://lists.apache.org/thread/l545m95xmf3w47oxwqxvg811or7b93tb > > [2]: https://lists.apache.org/thread/0vwj8gdo55jly5zn16wksrotyqqm0zqr > > >
Re: [ANNOUNCE] New Arrow committer: Eric Patrick Hanson
thanks, I'm excited to join! On 2022/10/26 21:38:53 Sutou Kouhei wrote: > On behalf of the Arrow PMC, I'm happy to announce that Eric Patrick Hanson > has accepted an invitation to become a committer on Apache > Arrow. Welcome, and thank you for your contributions! > > kou >
Re: [VOTE] Move issue tracking to GitHub Issues
+1 On 2022/10/26 23:02:33 Neal Richardson wrote: > I propose that we move issue tracking from the ASF's Jira to GitHub Issues. > This has been discussed on [1] and [2] and there seems to be consensus. A > number of Arrow subprojects already use GitHub Issues; this moves the issue > tracking for `apache/arrow` into GitHub along with the source code. > > The vote will be open for at least 72 hours. > > [ ] +1 Leave ASF Jira and move to GitHub Issues > [ ] +0 > [ ] -1 Remain in Jira because... > > My vote: +1 > > Neal > > > [1]: https://lists.apache.org/thread/l545m95xmf3w47oxwqxvg811or7b93tb > [2]: https://lists.apache.org/thread/0vwj8gdo55jly5zn16wksrotyqqm0zqr >
Re: [VOTE] Move issue tracking to GitHub Issues
+1 (non-binding)! On Thu, Oct 27, 2022 at 8:54 AM Eric Hanson wrote: > +1 > > On 2022/10/26 23:02:33 Neal Richardson wrote: > > I propose that we move issue tracking from the ASF's Jira to GitHub > Issues. > > This has been discussed on [1] and [2] and there seems to be consensus. A > > number of Arrow subprojects already use GitHub Issues; this moves the > issue > > tracking for `apache/arrow` into GitHub along with the source code. > > > > The vote will be open for at least 72 hours. > > > > [ ] +1 Leave ASF Jira and move to GitHub Issues > > [ ] +0 > > [ ] -1 Remain in Jira because... > > > > My vote: +1 > > > > Neal > > > > > > [1]: https://lists.apache.org/thread/l545m95xmf3w47oxwqxvg811or7b93tb > > [2]: https://lists.apache.org/thread/0vwj8gdo55jly5zn16wksrotyqqm0zqr > > >
Re: [VOTE] Move issue tracking to GitHub Issues
+1 On Thu, Oct 27, 2022 at 7:13 AM Dewey Dunnington wrote: > +1 (non-binding)! > > On Thu, Oct 27, 2022 at 8:54 AM Eric Hanson > wrote: > > > +1 > > > > On 2022/10/26 23:02:33 Neal Richardson wrote: > > > I propose that we move issue tracking from the ASF's Jira to GitHub > > Issues. > > > This has been discussed on [1] and [2] and there seems to be > consensus. A > > > number of Arrow subprojects already use GitHub Issues; this moves the > > issue > > > tracking for `apache/arrow` into GitHub along with the source code. > > > > > > The vote will be open for at least 72 hours. > > > > > > [ ] +1 Leave ASF Jira and move to GitHub Issues > > > [ ] +0 > > > [ ] -1 Remain in Jira because... > > > > > > My vote: +1 > > > > > > Neal > > > > > > > > > [1]: https://lists.apache.org/thread/l545m95xmf3w47oxwqxvg811or7b93tb > > > [2]: https://lists.apache.org/thread/0vwj8gdo55jly5zn16wksrotyqqm0zqr > > > > > >
Re: [VOTE] Move issue tracking to GitHub Issues
+1 On Thu, Oct 27, 2022 at 2:36 PM prem sagar gali wrote: > +1 > > On Thu, Oct 27, 2022 at 7:13 AM Dewey Dunnington > wrote: > > > +1 (non-binding)! > > > > On Thu, Oct 27, 2022 at 8:54 AM Eric Hanson > > wrote: > > > > > +1 > > > > > > On 2022/10/26 23:02:33 Neal Richardson wrote: > > > > I propose that we move issue tracking from the ASF's Jira to GitHub > > > Issues. > > > > This has been discussed on [1] and [2] and there seems to be > > consensus. A > > > > number of Arrow subprojects already use GitHub Issues; this moves the > > > issue > > > > tracking for `apache/arrow` into GitHub along with the source code. > > > > > > > > The vote will be open for at least 72 hours. > > > > > > > > [ ] +1 Leave ASF Jira and move to GitHub Issues > > > > [ ] +0 > > > > [ ] -1 Remain in Jira because... > > > > > > > > My vote: +1 > > > > > > > > Neal > > > > > > > > > > > > [1]: > https://lists.apache.org/thread/l545m95xmf3w47oxwqxvg811or7b93tb > > > > [2]: > https://lists.apache.org/thread/0vwj8gdo55jly5zn16wksrotyqqm0zqr > > > > > > > > > >
Re: [Discuss][Python] Stop publishing universal wheels?
Hello, if we have wheels for x86_64 and arm64 individually, I don't see an argument for keeping universal2 ones. x86_64 Macs will probably stay around for a while as Apple is quite good in keeping old hardware updated, and the laptops themselves are pretty solid. Best Uwe On Thu, Oct 27, 2022, at 10:04 AM, Antoine Pitrou wrote: > Hello, > > Currently, for macOS we're publishing both arm64, x86_64 *and* > universal2 binary wheels (the latter contain both arm64 and x86_64 code > in a single binary). > > Here are some observations from me: > > * Producing universal2 wheels is more complex than producing > single-architecture wheels (we actually have to build for both > architectures separately, then merge the results); it's also one more > CI/packaging configuration to look after > > * x86-64 Macs are legacy and are gradually disappearing (especially for > high-performance applications where ARM Macs are massively faster) > > * Numpy publishes only architecture-specific wheels, while Pandas > publishes both architecture-specific and universal wheels > > * Size-wise, a universal wheel is not much smaller than the sum of > architecture-specific wheels (for example, 43.7 MB for > pyarrow-9.0.0-cp310-cp310, vs. 24.0 MB + 21.6 MB) > > Is there any reason why we should continue publishing universal wheels > for macOS? > > Regards > > Antoine.
Re: [VOTE] Move issue tracking to GitHub Issues
+1 On Thu, 27 Oct 2022 at 14:00, Alenka Frim wrote: > +1 > > On Thu, Oct 27, 2022 at 2:36 PM prem sagar gali > wrote: > > > +1 > > > > On Thu, Oct 27, 2022 at 7:13 AM Dewey Dunnington > > wrote: > > > > > +1 (non-binding)! > > > > > > On Thu, Oct 27, 2022 at 8:54 AM Eric Hanson > > > wrote: > > > > > > > +1 > > > > > > > > On 2022/10/26 23:02:33 Neal Richardson wrote: > > > > > I propose that we move issue tracking from the ASF's Jira to GitHub > > > > Issues. > > > > > This has been discussed on [1] and [2] and there seems to be > > > consensus. A > > > > > number of Arrow subprojects already use GitHub Issues; this moves > the > > > > issue > > > > > tracking for `apache/arrow` into GitHub along with the source code. > > > > > > > > > > The vote will be open for at least 72 hours. > > > > > > > > > > [ ] +1 Leave ASF Jira and move to GitHub Issues > > > > > [ ] +0 > > > > > [ ] -1 Remain in Jira because... > > > > > > > > > > My vote: +1 > > > > > > > > > > Neal > > > > > > > > > > > > > > > [1]: > > https://lists.apache.org/thread/l545m95xmf3w47oxwqxvg811or7b93tb > > > > > [2]: > > https://lists.apache.org/thread/0vwj8gdo55jly5zn16wksrotyqqm0zqr > > > > > > > > > > > > > > >
Re: [ANNOUNCE] New Arrow committer: Ben Baumgold
Congratulations Ben! El jue, 27 oct 2022 a las 5:11, Weston Pace () escribió: > Congratulations Ben! > > On Wed, Oct 26, 2022 at 2:05 PM David Li wrote: > > > > Welcome Ben! > > > > On Wed, Oct 26, 2022, at 17:57, Ian Joiner wrote: > > > Congrats Ben! > > > > > > Ian > > > > > > On Wednesday, October 26, 2022, Sutou Kouhei > wrote: > > > > > >> On behalf of the Arrow PMC, I'm happy to announce that Ben Baumgold > > >> has accepted an invitation to become a committer on Apache > > >> Arrow. Welcome, and thank you for your contributions! > > >> > > >> kou > > >> >
Re: [VOTE] Move issue tracking to GitHub Issues
+1 On Thu, Oct 27, 2022, at 5:13 PM, Nic wrote: > +1 > > On Thu, 27 Oct 2022 at 14:00, Alenka Frim > wrote: > >> +1 >> >> On Thu, Oct 27, 2022 at 2:36 PM prem sagar gali >> wrote: >> >> > +1 >> > >> > On Thu, Oct 27, 2022 at 7:13 AM Dewey Dunnington >> > wrote: >> > >> > > +1 (non-binding)! >> > > >> > > On Thu, Oct 27, 2022 at 8:54 AM Eric Hanson >> > > wrote: >> > > >> > > > +1 >> > > > >> > > > On 2022/10/26 23:02:33 Neal Richardson wrote: >> > > > > I propose that we move issue tracking from the ASF's Jira to GitHub >> > > > Issues. >> > > > > This has been discussed on [1] and [2] and there seems to be >> > > consensus. A >> > > > > number of Arrow subprojects already use GitHub Issues; this moves >> the >> > > > issue >> > > > > tracking for `apache/arrow` into GitHub along with the source code. >> > > > > >> > > > > The vote will be open for at least 72 hours. >> > > > > >> > > > > [ ] +1 Leave ASF Jira and move to GitHub Issues >> > > > > [ ] +0 >> > > > > [ ] -1 Remain in Jira because... >> > > > > >> > > > > My vote: +1 >> > > > > >> > > > > Neal >> > > > > >> > > > > >> > > > > [1]: >> > https://lists.apache.org/thread/l545m95xmf3w47oxwqxvg811or7b93tb >> > > > > [2]: >> > https://lists.apache.org/thread/0vwj8gdo55jly5zn16wksrotyqqm0zqr >> > > > > >> > > > >> > > >> > >>
Re: [VOTE] Move issue tracking to GitHub Issues
+1 From: Uwe L. Korn Date: Thursday, October 27, 2022 at 10:22 AM To: dev@arrow.apache.org Subject: Re: [VOTE] Move issue tracking to GitHub Issues CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. +1 On Thu, Oct 27, 2022, at 5:13 PM, Nic wrote: > +1 > > On Thu, 27 Oct 2022 at 14:00, Alenka Frim > wrote: > >> +1 >> >> On Thu, Oct 27, 2022 at 2:36 PM prem sagar gali >> wrote: >> >> > +1 >> > >> > On Thu, Oct 27, 2022 at 7:13 AM Dewey Dunnington >> > wrote: >> > >> > > +1 (non-binding)! >> > > >> > > On Thu, Oct 27, 2022 at 8:54 AM Eric Hanson >> > > wrote: >> > > >> > > > +1 >> > > > >> > > > On 2022/10/26 23:02:33 Neal Richardson wrote: >> > > > > I propose that we move issue tracking from the ASF's Jira to GitHub >> > > > Issues. >> > > > > This has been discussed on [1] and [2] and there seems to be >> > > consensus. A >> > > > > number of Arrow subprojects already use GitHub Issues; this moves >> the >> > > > issue >> > > > > tracking for `apache/arrow` into GitHub along with the source code. >> > > > > >> > > > > The vote will be open for at least 72 hours. >> > > > > >> > > > > [ ] +1 Leave ASF Jira and move to GitHub Issues >> > > > > [ ] +0 >> > > > > [ ] -1 Remain in Jira because... >> > > > > >> > > > > My vote: +1 >> > > > > >> > > > > Neal >> > > > > >> > > > > >> > > > > [1]: >> > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fl545m95xmf3w47oxwqxvg811or7b93tb&data=05%7C01%7Cmatt.phelps%408451.com%7C17169903a26945db335608dab82f1a2f%7C5f9dc6bdf38a454a864cc803691193c5%7C0%7C0%7C638024809699659114%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=cbc4pEWsIlRSH2bLOcMVgDAMT2NM%2FeqG86FYv%2FPmaME%3D&reserved=0 >> > > > > [2]: >> > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2F0vwj8gdo55jly5zn16wksrotyqqm0zqr&data=05%7C01%7Cmatt.phelps%408451.com%7C17169903a26945db335608dab82f1a2f%7C5f9dc6bdf38a454a864cc803691193c5%7C0%7C0%7C638024809699659114%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=lkTheFeoBmRNQ0IeG5OA2f9TfW%2FZ52L4QEX3aTNexKs%3D&reserved=0 >> > > > > >> > > > >> > > >> > >>
Re: [VOTE] Move issue tracking to GitHub Issues
+1 On Thu, 27 Oct 2022 at 08:34, Matt Phelps wrote: > +1 > > From: Uwe L. Korn > Date: Thursday, October 27, 2022 at 10:22 AM > To: dev@arrow.apache.org > Subject: Re: [VOTE] Move issue tracking to GitHub Issues > CAUTION: This email originated from outside of the organization. Do not > click links or open attachments unless you recognize the sender and know > the content is safe. > > +1 > > On Thu, Oct 27, 2022, at 5:13 PM, Nic wrote: > > +1 > > > > On Thu, 27 Oct 2022 at 14:00, Alenka Frim .invalid> > > wrote: > > > >> +1 > >> > >> On Thu, Oct 27, 2022 at 2:36 PM prem sagar gali > >> wrote: > >> > >> > +1 > >> > > >> > On Thu, Oct 27, 2022 at 7:13 AM Dewey Dunnington > >> > wrote: > >> > > >> > > +1 (non-binding)! > >> > > > >> > > On Thu, Oct 27, 2022 at 8:54 AM Eric Hanson > > >> > > wrote: > >> > > > >> > > > +1 > >> > > > > >> > > > On 2022/10/26 23:02:33 Neal Richardson wrote: > >> > > > > I propose that we move issue tracking from the ASF's Jira to > GitHub > >> > > > Issues. > >> > > > > This has been discussed on [1] and [2] and there seems to be > >> > > consensus. A > >> > > > > number of Arrow subprojects already use GitHub Issues; this > moves > >> the > >> > > > issue > >> > > > > tracking for `apache/arrow` into GitHub along with the source > code. > >> > > > > > >> > > > > The vote will be open for at least 72 hours. > >> > > > > > >> > > > > [ ] +1 Leave ASF Jira and move to GitHub Issues > >> > > > > [ ] +0 > >> > > > > [ ] -1 Remain in Jira because... > >> > > > > > >> > > > > My vote: +1 > >> > > > > > >> > > > > Neal > >> > > > > > >> > > > > > >> > > > > [1]: > >> > > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fl545m95xmf3w47oxwqxvg811or7b93tb&data=05%7C01%7Cmatt.phelps%408451.com%7C17169903a26945db335608dab82f1a2f%7C5f9dc6bdf38a454a864cc803691193c5%7C0%7C0%7C638024809699659114%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=cbc4pEWsIlRSH2bLOcMVgDAMT2NM%2FeqG86FYv%2FPmaME%3D&reserved=0 > >> > > > > [2]: > >> > > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2F0vwj8gdo55jly5zn16wksrotyqqm0zqr&data=05%7C01%7Cmatt.phelps%408451.com%7C17169903a26945db335608dab82f1a2f%7C5f9dc6bdf38a454a864cc803691193c5%7C0%7C0%7C638024809699659114%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=lkTheFeoBmRNQ0IeG5OA2f9TfW%2FZ52L4QEX3aTNexKs%3D&reserved=0 > >> > > > > > >> > > > > >> > > > >> > > >> >
Re: [ANNOUNCE] New Arrow committer: Ben Baumgold
Congratulations! On Thu, Oct 27, 2022 at 11:21 AM Raúl Cumplido wrote: > Congratulations Ben! > > El jue, 27 oct 2022 a las 5:11, Weston Pace () > escribió: > > > Congratulations Ben! > > > > On Wed, Oct 26, 2022 at 2:05 PM David Li wrote: > > > > > > Welcome Ben! > > > > > > On Wed, Oct 26, 2022, at 17:57, Ian Joiner wrote: > > > > Congrats Ben! > > > > > > > > Ian > > > > > > > > On Wednesday, October 26, 2022, Sutou Kouhei > > wrote: > > > > > > > >> On behalf of the Arrow PMC, I'm happy to announce that Ben Baumgold > > > >> has accepted an invitation to become a committer on Apache > > > >> Arrow. Welcome, and thank you for your contributions! > > > >> > > > >> kou > > > >> > > >
Re: [ANNOUNCE] New Arrow committer: Ben Baumgold
Congrats Ben! Rok On Thu, Oct 27, 2022 at 5:53 PM Andrew Lamb wrote: > Congratulations! > > On Thu, Oct 27, 2022 at 11:21 AM Raúl Cumplido > wrote: > > > Congratulations Ben! > > > > El jue, 27 oct 2022 a las 5:11, Weston Pace () > > escribió: > > > > > Congratulations Ben! > > > > > > On Wed, Oct 26, 2022 at 2:05 PM David Li wrote: > > > > > > > > Welcome Ben! > > > > > > > > On Wed, Oct 26, 2022, at 17:57, Ian Joiner wrote: > > > > > Congrats Ben! > > > > > > > > > > Ian > > > > > > > > > > On Wednesday, October 26, 2022, Sutou Kouhei > > > wrote: > > > > > > > > > >> On behalf of the Arrow PMC, I'm happy to announce that Ben > Baumgold > > > > >> has accepted an invitation to become a committer on Apache > > > > >> Arrow. Welcome, and thank you for your contributions! > > > > >> > > > > >> kou > > > > >> > > > > > >
[Rust] Sync meetingThursday October 27, 2022
15:00 UTC Thursday October 27, 2022 Attendees: Batuhan, Wolfram Shulte, Michael Angerman, vin jake, Andy Grove, Andrew Lamb, Mustafa, Ian Joiner, Xudong Discussion topics: [Andrew Lamb] Ticket backlog, help reviewing PRs, Governance: #3957 [Batuhan Taskaya] Short & long term plans on improving statistics & CBOs (doc) There is more information and a link to the recording on [1] Andrew [1] https://docs.google.com/document/d/1atCVnoff5SR4eM4Lwf2M1BBJTY6g3_HUNR6qswYJW_U/edit#
[Rust][DataFusion] Proposed PR guidelines
There are some proposed guidelines[1] for PRs trying to formalize best practice as the community grows. We would welcome feedback. Andrew [1] https://github.com/apache/arrow-datafusion/pull/3985
Re: [VOTE] Move issue tracking to GitHub Issues
+1 On Thu, 27 Oct 2022 at 07:27, Jacob Quinn wrote: > > +1 > > On Wed, Oct 26, 2022 at 5:04 PM Neal Richardson > wrote: > > > I propose that we move issue tracking from the ASF's Jira to GitHub Issues. > > This has been discussed on [1] and [2] and there seems to be consensus. A > > number of Arrow subprojects already use GitHub Issues; this moves the issue > > tracking for `apache/arrow` into GitHub along with the source code. > > > > The vote will be open for at least 72 hours. > > > > [ ] +1 Leave ASF Jira and move to GitHub Issues > > [ ] +0 > > [ ] -1 Remain in Jira because... > > > > My vote: +1 > > > > Neal > > > > > > [1]: https://lists.apache.org/thread/l545m95xmf3w47oxwqxvg811or7b93tb > > [2]: https://lists.apache.org/thread/0vwj8gdo55jly5zn16wksrotyqqm0zqr > >
Re: [Discuss][Python] Stop publishing universal wheels?
The cibuildwheel documentation has a note about this (https://cibuildwheel.readthedocs.io/en/stable/faq/#universal2), quoting: > The dual-architecture universal2 has a few benefits, but a key benefit to > a universal wheel is that a user can bundle these wheels into an application > and ship a single binary. > > However, if you have a large library, then you might prefer to ship the two > single-arch wheels instead - x86_64 and arm64. In rare cases, you might want > to build all three, but in that case, pip will not download the universal > wheels, > because it prefers the most specific wheel available. So given that we are in the situation of having a large library, and already do provide the separate x86_64 and arm64 wheels (and thus pip will actually never use the universal2 wheel by default), I think it seems fine to drop the universal2 wheels. Joris On Thu, 27 Oct 2022 at 10:05, Antoine Pitrou wrote: > > > Hello, > > Currently, for macOS we're publishing both arm64, x86_64 *and* > universal2 binary wheels (the latter contain both arm64 and x86_64 code > in a single binary). > > Here are some observations from me: > > * Producing universal2 wheels is more complex than producing > single-architecture wheels (we actually have to build for both > architectures separately, then merge the results); it's also one more > CI/packaging configuration to look after > > * x86-64 Macs are legacy and are gradually disappearing (especially for > high-performance applications where ARM Macs are massively faster) > > * Numpy publishes only architecture-specific wheels, while Pandas > publishes both architecture-specific and universal wheels > > * Size-wise, a universal wheel is not much smaller than the sum of > architecture-specific wheels (for example, 43.7 MB for > pyarrow-9.0.0-cp310-cp310, vs. 24.0 MB + 21.6 MB) > > Is there any reason why we should continue publishing universal wheels > for macOS? > > Regards > > Antoine.
Re: [ANNOUNCE] New Arrow committer: Eric Patrick Hanson
Congratulations, and welcome Eric! On Thu, 27 Oct 2022 at 13:53, Eric Hanson wrote: > > thanks, I'm excited to join! > > On 2022/10/26 21:38:53 Sutou Kouhei wrote: > > On behalf of the Arrow PMC, I'm happy to announce that Eric Patrick Hanson > > has accepted an invitation to become a committer on Apache > > Arrow. Welcome, and thank you for your contributions! > > > > kou > >
Re: [ANNOUNCE] New Arrow committer: Ben Baumgold
Congratulations, and welcome Ben! On Thu, 27 Oct 2022 at 05:11, Weston Pace wrote: > > Congratulations Ben! > > On Wed, Oct 26, 2022 at 2:05 PM David Li wrote: > > > > Welcome Ben! > > > > On Wed, Oct 26, 2022, at 17:57, Ian Joiner wrote: > > > Congrats Ben! > > > > > > Ian > > > > > > On Wednesday, October 26, 2022, Sutou Kouhei wrote: > > > > > >> On behalf of the Arrow PMC, I'm happy to announce that Ben Baumgold > > >> has accepted an invitation to become a committer on Apache > > >> Arrow. Welcome, and thank you for your contributions! > > >> > > >> kou > > >>
Re: [ANNOUNCE] New Arrow committer: Bogumił Kamiński
Congrats! On Wed, 26 Oct 2022 at 23:56, Ian Joiner wrote: > > Congrats Bogumił! > > Ian > > On Tuesday, October 25, 2022, Sutou Kouhei wrote: > > > Hi, > > > > On behalf of the Arrow PMC, I'm happy to announce that Bogumił Kamiński > > has accepted an invitation to become a committer on Apache > > Arrow. Welcome, and thank you for your contributions! > > > > Thanks, > > -- > > kou > >
Re: [RESULT][VOTE] Release Apache Arrow 10.0.0 - RC0
- [?] Upload wheels/sdist to pypi Done: https://pypi.org/project/pyarrow/10.0.0 On Wed, 26 Oct 2022 at 13:56, Neal Richardson wrote: > > I will submit the R package to CRAN. > > Neal > > On Wed, Oct 26, 2022 at 4:40 AM Sutou Kouhei wrote: > > > Thanks!!! > > > > Current status: > > > > - [Done] Make the released version as “RELEASED” on JIRA > > - [Done] Make the CPP PARQUET related version as “RELEASED” on JIRA > > - [Done] Start the new version on JIRA on the ARROW project > > - [Done] Start the new version on JIRA for the related CPP PARQUET version > > - [Done] Merge changes on release branch to maintenance branch for patch > > releases > > - [Done] Upload source > > - [Done] Upload binaries > > - [PR] Update website > > - [PR] Update Homebrew packages > > - [kou] Update MSYS2 package > > - [kou] Upload RubyGems > > - [Done] Upload JS packages > > - [Done] Upload C# packages > > - [?] Update conda recipes > > - [?] Upload wheels/sdist to pypi > > - [Done] Publish Maven artifacts > > - [?] Update R packages > > - [?] Update vcpkg port > > - [Done] Bump versions > > - [Done] Update tags for Go modules > > - [?] Update docs > > - [kou] Remove old artifacts > > > > In <1eb698f7-0d96-caa0-3527-09ee0ec34...@python.org> > > "Re: [RESULT][VOTE] Release Apache Arrow 10.0.0 - RC0" on Wed, 26 Oct > > 2022 09:24:38 +0200, > > Antoine Pitrou wrote: > > > > > > > > Le 26/10/2022 à 07:37, Sutou Kouhei a écrit : > > >> Two more: > > >> - Make the CPP PARQUET related version as "RELEASED" on JIRA > > >> - Start the new version on JIRA for the related CPP PARQUET version > > >> I don't have admin permission on PARQUET. Could someone who > > >> has admin permission on PARQUET do them? > > > > > > Ok, I did it. > > > > > > Regards > > > > > > Antoine. > >
Re: [VOTE] Move issue tracking to GitHub Issues
+1 (Non-binding) On Thu, Oct 27, 2022, 4:19 PM Joris Van den Bossche < jorisvandenboss...@gmail.com> wrote: > +1 > > On Thu, 27 Oct 2022 at 07:27, Jacob Quinn wrote: > > > > +1 > > > > On Wed, Oct 26, 2022 at 5:04 PM Neal Richardson < > neal.p.richard...@gmail.com> > > wrote: > > > > > I propose that we move issue tracking from the ASF's Jira to GitHub > Issues. > > > This has been discussed on [1] and [2] and there seems to be > consensus. A > > > number of Arrow subprojects already use GitHub Issues; this moves the > issue > > > tracking for `apache/arrow` into GitHub along with the source code. > > > > > > The vote will be open for at least 72 hours. > > > > > > [ ] +1 Leave ASF Jira and move to GitHub Issues > > > [ ] +0 > > > [ ] -1 Remain in Jira because... > > > > > > My vote: +1 > > > > > > Neal > > > > > > > > > [1]: https://lists.apache.org/thread/l545m95xmf3w47oxwqxvg811or7b93tb > > > [2]: https://lists.apache.org/thread/0vwj8gdo55jly5zn16wksrotyqqm0zqr > > > >
Re: [ANNOUNCE] New Arrow PMC member: Nicola Crane
Congratulations! On Wed, Oct 26, 2022 at 4:56 PM Ian Joiner wrote: > > Congrats Nic! > > Ian > > On Tuesday, October 25, 2022, Sutou Kouhei wrote: > > > The Project Management Committee (PMC) for Apache Arrow has invited > > Nicola Crane to become a PMC member and we are pleased to announce > > that Nicola Crane has accepted. > > > > Congratulations and welcome! > >
Re: Apache Arrow filesystem question
I definitely think it would be a good thing to have a C++ ADLS filesystem interface that is on par in quality with our S3 and GCS C++ interfaces — these should also provide material performance benefits to Python users over a pure-Python interface (I'm not sure if pyarrow's S3 interface via C++ has been studied relative to s3fs but there should be performance benefits in many datasets interactions). On Wed, Oct 26, 2022 at 1:09 PM Lee, David wrote: > > Or this.. > > https://arrow.apache.org/docs/python/filesystems.html#using-fsspec-compatible-filesystems-with-arrow > > import adlfs > # ... load your credentials and configure the filesystem > fs = adlfs.AzureBlobFileSystem(account_name=account_name, > account_key=account_key) > > > -Original Message- > From: Lee, David > Sent: Wednesday, October 26, 2022 11:04 AM > To: dev@arrow.apache.org > Subject: RE: Apache Arrow filesystem question > > There are fsspec implementations to support other filesystems. > > https://pypi.org/project/pyarrowfs-adlgen2/ > > -Original Message- > From: Jerry Adair > Sent: Wednesday, October 26, 2022 10:59 AM > To: dev@arrow.apache.org > Subject: RE: Apache Arrow filesystem question > > External Email: Use caution with links and attachments > > > Hi- > > I am curious about the Apache Arrow filesystem support. I noticed that there > are classes for S3 and GCS. I am currently using those classes to read/write > from/to those cloud storage options. However I noticed that there is no > class for Azure (ADLS). And so I am curious why that is? Does anyone know? > > Thanks! > Jerry > > > This message may contain information that is confidential or privileged. If > you are not the intended recipient, please advise the sender immediately and > delete this message. See > http://www.blackrock.com/corporate/compliance/email-disclaimers for further > information. Please refer to > http://www.blackrock.com/corporate/compliance/privacy-policy for more > information about BlackRock’s Privacy Policy. > > > For a list of BlackRock's office addresses worldwide, see > http://www.blackrock.com/corporate/about-us/contacts-locations. > > © 2022 BlackRock, Inc. All rights reserved.
RE: Apache Arrow filesystem question
I agree. I already utilize the AWS and GCS classes. We have a customer need for ADLS & Parquet. I've recommended that we wait for the new implementation to become available in the next Arrow/Parquet C++ library release. In a way I am making a "bet" that the feature makes it into that release (11.0.0), so hopefully the contributors will make that happen. -Original Message- From: Wes McKinney Sent: Thursday, October 27, 2022 4:42 PM To: dev@arrow.apache.org Subject: Re: Apache Arrow filesystem question [You don't often get email from wesmck...@gmail.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] EXTERNAL I definitely think it would be a good thing to have a C++ ADLS filesystem interface that is on par in quality with our S3 and GCS C++ interfaces - these should also provide material performance benefits to Python users over a pure-Python interface (I'm not sure if pyarrow's S3 interface via C++ has been studied relative to s3fs but there should be performance benefits in many datasets interactions). On Wed, Oct 26, 2022 at 1:09 PM Lee, David wrote: > > Or this.. > > https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Farro > w.apache.org%2Fdocs%2Fpython%2Ffilesystems.html%23using-fsspec-compati > ble-filesystems-with-arrow&data=05%7C01%7CJerry.Adair%40sas.com%7C > b0f839fa00934e9b49ce08dab8644346%7Cb1c14d5c362545b3a4309552373a0c2f%7C > 0%7C0%7C638025038018602431%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDA > iLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sd > ata=gnpmJKK3%2FcuYbnNlhEr%2F4notr7lCf0F9dJFTH8IeqYA%3D&reserved=0 > > import adlfs > # ... load your credentials and configure the filesystem fs = > adlfs.AzureBlobFileSystem(account_name=account_name, > account_key=account_key) > > > -Original Message- > From: Lee, David > Sent: Wednesday, October 26, 2022 11:04 AM > To: dev@arrow.apache.org > Subject: RE: Apache Arrow filesystem question > > There are fsspec implementations to support other filesystems. > > https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpypi > .org%2Fproject%2Fpyarrowfs-adlgen2%2F&data=05%7C01%7CJerry.Adair%4 > 0sas.com%7Cb0f839fa00934e9b49ce08dab8644346%7Cb1c14d5c362545b3a4309552 > 373a0c2f%7C0%7C0%7C638025038018602431%7CUnknown%7CTWFpbGZsb3d8eyJWIjoi > MC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7 > C%7C&sdata=Zhzd2XQa1pAkKYolRG4%2Bvgpr%2Fk7tmKSv6fL11Kg5xIg%3D& > reserved=0 > > -Original Message- > From: Jerry Adair > Sent: Wednesday, October 26, 2022 10:59 AM > To: dev@arrow.apache.org > Subject: RE: Apache Arrow filesystem question > > External Email: Use caution with links and attachments > > > Hi- > > I am curious about the Apache Arrow filesystem support. I noticed that there > are classes for S3 and GCS. I am currently using those classes to read/write > from/to those cloud storage options. However I noticed that there is no > class for Azure (ADLS). And so I am curious why that is? Does anyone know? > > Thanks! > Jerry > > > This message may contain information that is confidential or privileged. If > you are not the intended recipient, please advise the sender immediately and > delete this message. See > https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.blackrock.com%2Fcorporate%2Fcompliance%2Femail-disclaimers&data=05%7C01%7CJerry.Adair%40sas.com%7Cb0f839fa00934e9b49ce08dab8644346%7Cb1c14d5c362545b3a4309552373a0c2f%7C0%7C0%7C638025038018602431%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=a7lIrYIWXA3WNA%2Bc%2BRFvY952NWyjb3f03WLxUeOfOY4%3D&reserved=0 > for further information. Please refer to > https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.blackrock.com%2Fcorporate%2Fcompliance%2Fprivacy-policy&data=05%7C01%7CJerry.Adair%40sas.com%7Cb0f839fa00934e9b49ce08dab8644346%7Cb1c14d5c362545b3a4309552373a0c2f%7C0%7C0%7C638025038018602431%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=X93wWDdHJ6oPQT1S8sZqURTZl1borPzC8VCRisblioI%3D&reserved=0 > for more information about BlackRock's Privacy Policy. > > > For a list of BlackRock's office addresses worldwide, see > https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.blackrock.com%2Fcorporate%2Fabout-us%2Fcontacts-locations&data=05%7C01%7CJerry.Adair%40sas.com%7Cb0f839fa00934e9b49ce08dab8644346%7Cb1c14d5c362545b3a4309552373a0c2f%7C0%7C0%7C638025038018602431%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=okDt4J9JZ78nIOx913vltrblW%2B9XFTJpUpNOv%2BthNwA%3D&reserved=0. > > (c) 2022 BlackRock, Inc. All rights reserved.
[ANNOUNCE] New Arrow committer: Will Jones
On behalf of the Arrow PMC, I'm happy to announce that Will Jones has accepted an invitation to become a committer on Apache Arrow. Welcome, and thank you for your contributions! kou
Re: [ANNOUNCE] New Arrow committer: Will Jones
Congrats & welcome, Will! On Thu, Oct 27, 2022, at 19:56, Sutou Kouhei wrote: > On behalf of the Arrow PMC, I'm happy to announce that Will Jones > has accepted an invitation to become a committer on Apache > Arrow. Welcome, and thank you for your contributions! > > kou
Re: [ANNOUNCE] New Arrow committer: Will Jones
Congratulations Will! On Thu, Oct 27, 2022 at 19:56 Sutou Kouhei wrote: > On behalf of the Arrow PMC, I'm happy to announce that Will Jones > has accepted an invitation to become a committer on Apache > Arrow. Welcome, and thank you for your contributions! > > kou >
Re: [ANNOUNCE] New Arrow committer: Will Jones
Congrats Will! On Thu, Oct 27, 2022 at 9:02 PM Ian Cook wrote: > Congratulations Will! > > On Thu, Oct 27, 2022 at 19:56 Sutou Kouhei wrote: > > > On behalf of the Arrow PMC, I'm happy to announce that Will Jones > > has accepted an invitation to become a committer on Apache > > Arrow. Welcome, and thank you for your contributions! > > > > kou > > >
Re: [ANNOUNCE] New Arrow committer: Will Jones
congrats! On Thu, Oct 27, 2022 at 9:03 PM Matt Topol wrote: > Congrats Will! > > On Thu, Oct 27, 2022 at 9:02 PM Ian Cook wrote: > > > Congratulations Will! > > > > On Thu, Oct 27, 2022 at 19:56 Sutou Kouhei wrote: > > > > > On behalf of the Arrow PMC, I'm happy to announce that Will Jones > > > has accepted an invitation to become a committer on Apache > > > Arrow. Welcome, and thank you for your contributions! > > > > > > kou > > > > > >
Re: [ANNOUNCE] New Arrow committer: Will Jones
Congratulations Will! On Fri, Oct 28, 2022 at 6:40 AM Li Jin wrote: > congrats! > > On Thu, Oct 27, 2022 at 9:03 PM Matt Topol wrote: > > > Congrats Will! > > > > On Thu, Oct 27, 2022 at 9:02 PM Ian Cook wrote: > > > > > Congratulations Will! > > > > > > On Thu, Oct 27, 2022 at 19:56 Sutou Kouhei wrote: > > > > > > > On behalf of the Arrow PMC, I'm happy to announce that Will Jones > > > > has accepted an invitation to become a committer on Apache > > > > Arrow. Welcome, and thank you for your contributions! > > > > > > > > kou > > > > > > > > > >
Re: [ANNOUNCE] New Arrow committer: Will Jones
Congratulations Will! On Thu, Oct 27, 2022 at 6:51 PM Vibhatha Abeykoon wrote: > Congratulations Will! > > On Fri, Oct 28, 2022 at 6:40 AM Li Jin wrote: > > > congrats! > > > > On Thu, Oct 27, 2022 at 9:03 PM Matt Topol > wrote: > > > > > Congrats Will! > > > > > > On Thu, Oct 27, 2022 at 9:02 PM Ian Cook > wrote: > > > > > > > Congratulations Will! > > > > > > > > On Thu, Oct 27, 2022 at 19:56 Sutou Kouhei > wrote: > > > > > > > > > On behalf of the Arrow PMC, I'm happy to announce that Will Jones > > > > > has accepted an invitation to become a committer on Apache > > > > > Arrow. Welcome, and thank you for your contributions! > > > > > > > > > > kou > > > > > > > > > > > > > > >
Re: [ANNOUNCE] New Arrow committer: Will Jones
=) On Thu, 27 Oct 2022 at 16:56, Sutou Kouhei wrote: > On behalf of the Arrow PMC, I'm happy to announce that Will Jones > has accepted an invitation to become a committer on Apache > Arrow. Welcome, and thank you for your contributions! > > kou >
Re: [RESULT][VOTE] Release Apache Arrow 10.0.0 - RC0
Thanks! Current status: - [Done] Make the released version as “RELEASED” on JIRA - [Done] Make the CPP PARQUET related version as “RELEASED” on JIRA - [Done] Start the new version on JIRA on the ARROW project - [Done] Start the new version on JIRA for the related CPP PARQUET version - [Done] Merge changes on release branch to maintenance branch for patch releases - [Done] Upload source - [Done] Upload binaries - [Done] Update website - [PR] Update Homebrew packages - [kou] Update MSYS2 package - [kou] Upload RubyGems - [Done] Upload JS packages - [Done] Upload C# packages - [?] Update conda recipes - [Done] Upload wheels/sdist to pypi - [Done] Publish Maven artifacts - [Neal] Update R packages - [?] Update vcpkg port - [Done] Bump versions - [Done] Update tags for Go modules - [Done] Update docs - [kou] Remove old artifacts In "Re: [RESULT][VOTE] Release Apache Arrow 10.0.0 - RC0" on Thu, 27 Oct 2022 21:44:46 +0200, Joris Van den Bossche wrote: > - [?] Upload wheels/sdist to pypi > > Done: https://pypi.org/project/pyarrow/10.0.0 > > On Wed, 26 Oct 2022 at 13:56, Neal Richardson > wrote: >> >> I will submit the R package to CRAN. >> >> Neal >> >> On Wed, Oct 26, 2022 at 4:40 AM Sutou Kouhei wrote: >> >> > Thanks!!! >> > >> > Current status: >> > >> > - [Done] Make the released version as “RELEASED” on JIRA >> > - [Done] Make the CPP PARQUET related version as “RELEASED” on JIRA >> > - [Done] Start the new version on JIRA on the ARROW project >> > - [Done] Start the new version on JIRA for the related CPP PARQUET version >> > - [Done] Merge changes on release branch to maintenance branch for patch >> > releases >> > - [Done] Upload source >> > - [Done] Upload binaries >> > - [PR] Update website >> > - [PR] Update Homebrew packages >> > - [kou] Update MSYS2 package >> > - [kou] Upload RubyGems >> > - [Done] Upload JS packages >> > - [Done] Upload C# packages >> > - [?] Update conda recipes >> > - [?] Upload wheels/sdist to pypi >> > - [Done] Publish Maven artifacts >> > - [?] Update R packages >> > - [?] Update vcpkg port >> > - [Done] Bump versions >> > - [Done] Update tags for Go modules >> > - [?] Update docs >> > - [kou] Remove old artifacts >> > >> > In <1eb698f7-0d96-caa0-3527-09ee0ec34...@python.org> >> > "Re: [RESULT][VOTE] Release Apache Arrow 10.0.0 - RC0" on Wed, 26 Oct >> > 2022 09:24:38 +0200, >> > Antoine Pitrou wrote: >> > >> > > >> > > Le 26/10/2022 à 07:37, Sutou Kouhei a écrit : >> > >> Two more: >> > >> - Make the CPP PARQUET related version as "RELEASED" on JIRA >> > >> - Start the new version on JIRA for the related CPP PARQUET version >> > >> I don't have admin permission on PARQUET. Could someone who >> > >> has admin permission on PARQUET do them? >> > > >> > > Ok, I did it. >> > > >> > > Regards >> > > >> > > Antoine. >> >
