Re: [VOTE][Julia] Release Apache Arrow Julia 2.4.3 RC1

+1 Ran on macos m1. -Jacob On Thu, Feb 2, 2023 at 7:53 PM Sutou Kouhei wrote: > +1 > > I ran the following command line on Debian GNU/Linux sid: > > VERIFY_FORCE_USE_JULIA_BINARY=1 dev/release/verify_rc.sh 2.4.3 1 > > > Thanks, > -- > kou > > > In <20230203.113400.196149433832986@cle

Re: [VOTE][Julia] Release Apache Arrow Julia 2.4.3 RC1

+1 I ran the following command line on Debian GNU/Linux sid: VERIFY_FORCE_USE_JULIA_BINARY=1 dev/release/verify_rc.sh 2.4.3 1 Thanks, -- kou In <20230203.113400.196149433832986@clear-code.com> "[VOTE][Julia] Release Apache Arrow Julia 2.4.3 RC1" on Fri, 03 Feb 2023 11:34:00 +090

[VOTE][Julia] Release Apache Arrow Julia 2.4.3 RC1

Hi, I would like to propose the following release candidate (RC1) of Apache Arrow Julia version 2.4.3. This release candidate is based on commit: 8c0cc4498801758064bd72ffa2fa6460cfc51fdc [1] The source release rc1 is hosted at [2]. Please download, verify checksums and signatures, run the unit

[Python] Add ClientCookieMiddleware

Hi there, I'm a contributor for Dremio's Python Arrow Flight Client example. We currently implement CookieMiddleware to

[GitHub] [arrow-ballista-python] andygrove merged pull request #2: Add .asf.yaml

andygrove merged PR #2: URL: https://github.com/apache/arrow-ballista-python/pull/2 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@arro

[GitHub] [arrow-ballista-python] andygrove commented on pull request #1: Move the `python` directory of `arrow-ballista` to the new `arrow-ballista-python` repo

andygrove commented on PR #1: URL: https://github.com/apache/arrow-ballista-python/pull/1#issuecomment-1414528630 I think this is fine to unblock the development of Ballista core, but I we should at least enable the RAT check in this PR to ensure that no code gets checked in without the ap

[GitHub] [arrow-ballista-python] iajoiner commented on pull request #1: Move the `python` directory of `arrow-ballista` to the new `arrow-ballista-python` repo

iajoiner commented on PR #1: URL: https://github.com/apache/arrow-ballista-python/pull/1#issuecomment-1414407993 @andygrove -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment.

Re: [DISCUSS] PR automation workflow

A process that we use in arrow-rs / arrow-datafusion, which is less precise but seems to be working well enough at the moment, is : 1. Mark PRs that have received feedback and need more work prior to merge from `Ready to Review` back to `Draft` 2. Ask the author to set it back to "ready to revie

Re: [FlightSQL] servers / client reference implementations supporting parameterized statements

Thank you -- this is super helpful Andrew On Wed, Feb 1, 2023 at 12:47 PM Matt Topol wrote: > To this point, the Go flightsql sqlite server example is used to test the > Parameter Support for the ADBC flightsql driver: > - CI: > > https://github.com/apache/arrow-adbc/blob/main/.github/workflow

Re: [C++] Parquet and Arrow overlap

Day to day, I think having Parquet-cpp under the Apache Arrow project could make sense. Though I worry about two risks: 1. Would that lead to the governance of the format itself to be primarily the responsibility of the developers of Parquet-MR? 2. Would C++ developers interested in working with P

Re: [DISCUSS] Fixed shape tensor Canonical Extension Type

Hi Alenka, Great work on the RFC, I'm super excited to see this! I was planning to open a similar RFC at some point over the next few weeks, so this just saved me a bunch of work. :D At the Ray project [1], we've developed two tensor extension types (originally adapted from the tensor extension t

[DISCUSS] Fixed shape tensor Canonical Extension Type

Hi all! There have been quite a lot of discussions connected to the tensor support in Arrow Tables/RecorBatches. Issues to add support for a column in an Arrow table that has value cells each containing a tensor value, with all tensors having the same shape/dimensions [1] and a separate one for va

Re: [C++] Parquet and Arrow overlap

Would it make sense to transfer all governance of the parquet-cpp implementation to Apache Arrow? It seems like that's where we de facto are already, so that would resolve these ambiguities and put it in line with the Rust implementation. Would the Parquet PMC be opposed to formalizing this change

Re: [RESULT][VOTE] Release Apache Arrow 11.0.0 - RC0

Hi, The current status of the post-release tasks. I will follow up on them. Thanks everyone! - [done] Update the released milestone Date and set to "Closed" on GitHub - [done] Merge changes on release branch to maintenance branch for patch releases - [done] Add the new release to the Apache Repor

[ANNOUNCE] Apache Arrow 11.0.0 released

The Apache Arrow community is pleased to announce the 11.0.0 release. It includes 423 resolved issues ([1]) since the 10.0.1 release. The release is available now from our website and [2]: http://arrow.apache.org/install/ Read about what's new in the release https://arrow.apache.org/blog/2023

Re: [C++] Parquet and Arrow overlap

Hi, Does the parquet rust implementation have a similar issue? Similar to the C++ implementation, the Rust implementation lives under the Apache Arrow umbrella and does not have any direct affiliation with the Apache Parquet project that I am aware of, beyond using the same format specifica

Re: [C++] Parquet and Arrow overlap

Hi, I just wanted to add that with the recent migration to GitHub issues for Arrow we have updated our development tools (merge script, archery release tasks, ...) to work with GitHub but we haven't been able to drop JIRA support due to having to support Parquet issues. This makes us have to suppo

Re: [DISCUSS] PR automation workflow

Hi Raul, Since I'm the one who proposed that we reuse CPython's existing workflow infrastructure, it follows logically that I'm in favour :-) I'm a CPython core developer myself (though inactive lately), I will add that this workflow is really easing the work of reviewing PRs, as it makes

Re: [C++] Parquet and Arrow overlap

Hi Will, Le 01/02/2023 à 20:27, Will Jones a écrit : First, it's not obvious where issues are supposed to be open: In Parquet Jira or Arrow GitHub issues. Looking back at some of the original discussion, it looks like the intention was * use PARQUET-XXX for issues relating to Parquet core *