DISCUSS: Stabilize Arrow C Stream Interface?

The Arrow C Stream Interface is still listed as experimental [1], though it was introduced about 20 months ago [2]. It's being used in the well-advertised integration between PyArrow/R arrow and DuckDB [3]. Support was added to both Rust implementations [4][5]. It was discussed in today's sync

Re: design for Python UDFs in an Ibis/Substrait/Arrow workflow

Thanks, Weston. I was able to locally build a PoC of this to work for UDFs with some limitations - see details below. I'd like to get feedback about whether this approach is acceptable. If so, I could start contributing its components. With respect to Li's design points: 1. A way to

Re: Arrow sync call May 25 at 12:00 US/Eastern, 16:00 UTC

Below are the minutes of the call. Best, Rok Present: Dewey Dunnington, Raul Cumplido, Will Jones, Jonathan Keane, Matt Topol, Rok Mihevc, Ian Joiner Agenda: 1. Minimal C++/C interface 2. Naming the C++ Compute Engine 3. Change to bucket creation behaviour in S3FileSystem Notes: 1. Dewey is

Existence/name/scope for minimal C/C++ Arrow C Data interface helpers

I'm writing to gauge interest in a set of helpers in C and/or C++ for reading/exporting Arrow C Data interface structures. My use-case is building Arrow geospatial support in R [1], and while the set of helpers I've been using [2] has served the purpose of me writing about the opportunities for

Arrow sync call May 25 at 12:00 US/Eastern, 16:00 UTC

Hi all, Our biweekly sync call is today at 12:00 noon Eastern time. The Zoom meeting URL for this and other biweekly Arrow sync calls is: https://zoom.us/j/87649033008?pwd=SitsRHluQStlREM0TjJVYkRibVZsUT09 Alternatively, enter this information into the Zoom website or app to join the call:

[DISC][Java]: Migrate Arrow Java to JPMS Java Platform Module System

Hi All, This email's purpose is a request for comments to migrate Arrow Java to JPMS Java Platform Module System JSE 9+ (1). Current status: - Arrow Java use JSE1.8 specification - Arrow Java works with JSE1.8/9/11/17 - This is possible because

Re: Merge a pull request with GitHub API

+1 on the change, regardless of the discussion around merge button vs script, already starting to "merge" the PR through the script is certainly an improvement! On Tue, 24 May 2022 at 23:16, Sutou Kouhei wrote: > Hi, > > Do you have any objections to this? If nobody objects this, > I'll merge