+1
On Mon, May 19, 2025 at 6:24 PM Sutou Kouhei wrote:
>
> Hi,
>
> I would like to propose splitting the Swift implementation
> to its own repository.
>
> Motivation:
>
> * We want to make the Swift implementation Swift Package
> Manager compatible.
> * It requires a top-level Package.swift.
Thanks for this Kou. I think the change makes sense and is a good idea.
On Fri, May 16, 2025 at 1:49 AM Sutou Kouhei wrote:
>
> Hi,
>
> This is a similar discussion to the "[DISCUSS] Split Go
> release process" thread[1], the "[DISCUSS] Split Java
> release process" thread[2], the "[DISCUSS] Spli
+1 (binding)
On Wed, May 7, 2025 at 1:48 AM Raúl Cumplido wrote:
>
> Hi,
>
> I would like to propose splitting the JS implementation and the
> corresponding release process to its own repository.
>
> Motivation:
>
> * We want to reduce needless major releases to avoid unnecessary user
> burden.
>
(or whatever version someone is willing to rebase
> onto, for as long as they're willing to rebase it).
>
> Is there a way to do this that doesn't essentially look like [1]?
>
> [1]: https://github.com/uccross/skyhookdm-arrow
>
>
> -Aldrin
>
>
> On Mon, May 5, 2
+1 for deprecating. I think it would be great if we could find a
volunteer to move it into a standalone or contrib repo so it's easy to
find rather than removing it from the source tree.
On Mon, May 5, 2025 at 1:05 AM Antoine Pitrou wrote:
>
>
> Hello,
>
> "Skyhook" is a little-known C++ componen
Thanks to everyone who was able to join today. For those unable to
attend, we took notes [1] and please flag me/others down if you need
any more info.
[1]
https://docs.google.com/document/d/1xrji8fc6_24TVmKiHJB4ECX1Zy2sy2eRbBjpVJMnPmk
On Wed, Apr 23, 2025 at 6:33 AM Ian Cook wrote:
>
> Our nex
ternate interfaces such as the uri-and-kv-pairs which Raphael
> described
> would be possible, sorry for the confusion; I definitely did not mean MUST
> in an rfc2119
> sense.
>
> [1]
> https://arrow.apache.org/docs/cpp/api/filesystem.html#high-level-factory-functions
>
> On Wed,
Hi Ben, would you be able to elaborate on this part:
> Since URIs must be complete specifications of a filesystem, this necessitates
> inclusion of the secrets required by S3 in the URI. Since anyone with a URI
> has access to the filesystem to which it refers, these filesystem URIs are
> trans
Congrats Rok!
On Wed, Mar 19, 2025 at 12:10 PM Antoine Pitrou wrote:
>
>
> Hello all,
>
> The Project Management Committee (PMC) for Apache Arrow has invited
> Rok Mihevc to become a PMC member and we are pleased to announce that
> Rok has accepted.
>
> Regards
>
> Antoine.
I can't make it today but I put in a note about the upcoming monorepo
20.0.0 [1] feature freeze [2] with some links.
[1] https://github.com/apache/arrow/milestone/65
[2] https://lists.apache.org/thread/9d2sv5rpnr160prp2c4z8s9zk39mb1xz
On Wed, Mar 26, 2025 at 3:48 AM Ian Cook wrote:
>
> Our next
Congrats!
On Fri, Mar 21, 2025 at 1:51 PM Andrew Lamb wrote:
>
> Hi,
>
> On behalf of the Arrow PMC, I'm happy to announce that Matthijs Brobbel
> has accepted an invitation to become a committer on Apache
> Arrow. Welcome, and thank you for your contributions!
>
> Andrew
+1
On Thu, Mar 20, 2025 at 9:50 PM Sutou Kouhei wrote:
>
> Hi,
>
> I would like to propose enabling GitHub Discussions on:
>
> * apache/arrow
> * apache/arrow-adbc
> * apache/arrow-cookbook
> * apache/arrow-experiments
> * apache/arrow-flight-sql-postgresql
> * apache/arrow-go
> * apache/arrow-ja
Congratulations Ian!
On Thu, Mar 20, 2025 at 1:05 AM Sutou Kouhei wrote:
>
> The Project Management Committee (PMC) for Apache Arrow has invited
> Ian Cook to become a PMC member and we are pleased to announce
> that Ian Cook has accepted.
>
> Congratulations and welcome!
+1
PS: Before we create the repo, we might discuss whether it should be
called arrow-csharp or arrow-dotnet. I think the latter makes more
sense.
On Sun, Mar 16, 2025 at 6:13 PM Sutou Kouhei wrote:
>
> Hi,
>
> I would like to propose splitting C# release process.
>
> Motivation:
>
> * We want to
Congrats!
On Sun, Mar 16, 2025 at 10:23 PM Sutou Kouhei wrote:
>
> The Project Management Committee (PMC) for Apache Arrow has invited
> Jacob Wujciak to become a PMC member and we are pleased to announce
> that Jacob Wujciak has accepted.
>
> Congratulations and welcome!
>
>
Congrats JB. And welcome.
On Sun, Mar 9, 2025 at 11:05 PM Sutou Kouhei wrote:
>
> Hi,
>
> On behalf of the Arrow PMC, I'm happy to announce that
> Jean-Baptiste Onofré has accepted an invitation to become a
> committer on Apache Arrow. Welcome, and thank you for your
> contributions!
>
> Thanks,
I think this is a good idea.
A possible reason for hesitation is that it provides us yet another
stream that requires maintainer attention. But it also occurs to me
that a new stream of information on GitHub may be significantly more
accessible than a stream on a mailing list or third-party websit
Hi Kou, thanks for proposing this.
I think it makes sense and sounds like a good thing to do. I'm happy
to help with migration tasks and releases.
On Wed, Mar 12, 2025 at 7:51 PM Sutou Kouhei wrote:
>
> Hi,
>
> This is a similar discussion to the "[DISCUSS] Split Go
> release process" thread[1],
+1 (binding)
I ran `dev/release/verify_rc.sh 18.2.0 1` on macOS 15 (aarch64).
On Wed, Mar 12, 2025 at 11:07 AM Matt Topol wrote:
>
> Hi,
>
> I would like to propose the following release candidate (RC1) of
> Apache Arrow Go version 18.2.0.
>
> This release candidate is based on commit:
> 166cf7b
+0
I ran dev/release/verify_rc.sh 18.2.0 on macOS aarch64 and got
failures in the Parquet encryption suite [1].
It looks like it's because the encryption test files in
parquet-testing were updated in [2]. arrow-go is pinned to an earlier
version of parquet-testing, its tests pass against that ver
It seems like there are currently more advantages to keeping R in the
monorepo for the time being than there are advantages to splitting it
out.
I'll add that the Python and R implementations routinely benefit from
being in the monorepo when contributions to Arrow C++ often need to be
propagated i
+1 (binding)
Verified on macOS 15 (aarch64) with
`dev/release/verify-release-candidate.sh 17 0` after a few tweaks:
- Added libpq and brew sqlite to PKG_CONFIG_PATH
- Installed the apache-arrow-glib brew formula from a local copy with
`"-Dvapi=true"` added to the meson setup build command
On Sun
The Apache Arrow community is pleased to announce the 19.0.1 release.
It includes 12 resolved issues [1] since the 19.0.0 release.
The release is available now from our website and [2]:
https://arrow.apache.org/install/
Read about what's new in the release at:
https://arrow.apache.org/blo
Hi all,
A regression was encountered [1] while updating the arrow-cpp
conda-forge feedstock for Arrow 19.0.1. The proximate issue may be
that conda-forge doesn't do unity builds and our CI didn't catch the
ultimate issue which appears to be a missing include.
Can others please take a look at the
tasks.
On Wed, Feb 12, 2025 at 6:23 PM Bryce Mecum wrote:
>
> Hi,
>
> I would like to propose the following release candidate (RC1) of Apache
> Arrow version 19.0.1. This is a release consisting of 12
> resolved GitHub issues[1].
>
> This release
2025 at 2:12 PM Ruoxi Sun wrote:
> > >
> > > > +1 (non-binding)
> > > >
> > > > On my M1 Mac, OS version Sonoma 14.7.1 (23H222), AppleClang
> > > > 15.0.0.15000309, verified cpp:
> > > >
> > > > TEST_DEFAULT=0 TEST_CPP=1 ./ver
Hi,
I would like to propose the following release candidate (RC1) of Apache
Arrow version 19.0.1. This is a release consisting of 12
resolved GitHub issues[1].
This release candidate is based on commit:
272715f6df2a042d69881ffa03d5078c58e4b345 [2]
The source release rc1 is hosted at [3].
The bin
+1 (binding)
Verified on macOS 15.3 (aarch64)
On Wed, Feb 12, 2025 at 7:40 AM Andrew Lamb wrote:
>
> Hi,
>
> I would like to propose a release of Apache Arrow Rust Implementation,
> version 54.2.0.
>
> This release candidate is based on commit:
> d4b9482f5dee47a0f2f7afc129db83b8ac8df406 [1]
>
>
Thanks Antoine and thanks everyone. I consider it a great honor to get
to work with such an amazing group of people on this project.
On Wed, Feb 5, 2025 at 11:24 AM Antoine Pitrou wrote:
>
>
> Hello,
>
> The Project Management Committee (PMC) for Apache Arrow has invited
> Bry
, 2025 at 1:05 PM Bryce Mecum wrote:
>
> Just an update: The 19.0.1 milestone can now be considered frozen with 8
> total issues. Thanks everyone for the help flagging extra issues to go into
> the release and for getting patches in promptly.
>
> I'll start working on creat
https://github.com/apache/arrow/milestone/68?closed=1
On 2025/01/24 01:08:48 Bryce Mecum wrote:
> Hello all,
>
> A bug [1] has been identified in the 19.0.0 release affecting the C++
> and Python implementations. See the Arrow 19.0.0 blog post [2] for
> more details. After discussion on Zulip
Hello Parquet community,
The Arrow project recently fixed a bug [1] in its C++ Parquet
implementation that was causing compliant Parquet files written by
recent versions of parquet-rs [2] to be unreadable by the C++
implementation due to differences in the implementation of Parquet’s
SizeStatistic
Hello all,
A bug [1] has been identified in the 19.0.0 release affecting the C++
and Python implementations. See the Arrow 19.0.0 blog post [2] for
more details. After discussion on Zulip [3], it was decided to
undertake a 19.0.1 release to address it.
We've created a 19.0.1 milestone on GitHub [
The Apache Arrow community is pleased to announce the 19.0.0 release.
It includes 202 resolved issues [1] since the 18.1.0 release.
The release is available now from our website and [2]:
https://arrow.apache.org/install/
Read about what's new in the release at:
https://arrow.apache.org/bl
I think we should allow multiple PRs for any issue in order to reduce
friction for contributors.
I remembered this thread while looking at the issue for Decimal32/64
support [1] which I think is a good example of where filing separate
issues for every patch doesn't add value and adds friction. Som
github.com/apache/arrow/issues/45264
Waiting to start:
- Update version in Apache Arrow Cookbook (blocked by conda-forge)
- Announce the new release
- Publish release blog posts
- Announce the release on Twitter
- Remove old artifacts
On 2025/01/15 19:27:00 Bryce Mecum wrote:
> The vote carr
The vote carries with 4 +1 binding votes, 1 +1 non-binding vote and no -1 votes.
Thanks everyone for taking the time to help verify the release and to
Kou for help creating the RC. I'll start on the post-release tasks
today.
The vote carries with 4 +1 binding votes, 1 +1 non-binding vote and no -1 votes.
Thanks everyone for taking the time to help verify the release and to
Kou for help creating the RC. I'll start on the post-release tasks
today.
On Sun, Jan 12, 2025 at 10:11 AM Bryce Mecum wrote:
>
>
Thanks Kou and David. I've just sent an email to start the vote thread
for Arrow 19.0.0 RC0.
On Sun, Jan 12, 2025 at 3:15 AM David Li wrote:
>
> Let's have Arrow proceed and then I'll start RC2 afterwards (to fix the R
> docs issue).
>
> On Sun, Jan 12, 2025, at 11:27, Sutou Kouhei wrote:
> > -1
Hi,
I would like to propose the following release candidate (RC0) of Apache
Arrow version 19.0.0. This is a release consisting of 198
resolved GitHub issues[1].
This release candidate is based on commit:
400b068b45aa06160963e8de2c21d026dbe0d4ac [2]
The source release rc0 is hosted at [3].
The bi
+1 (non-binding)
Verified on macOS 15.1.1 (aarch64).
On Thu, Jan 9, 2025 at 12:37 PM Matt Topol wrote:
>
> Hi,
>
> I would like to propose the following release candidate (RC0) of
> Apache Arrow Go version 18.1.0.
>
> This release candidate is based on commit:
> 58255a7d3a16b2fa7e3cd118e8770f341
+1 (non-binding)
Verified on Windows 11 x86_64 by running
`.\dev\release\verify-release-candidate.ps1 16 0`.
(I did have to modify the Join-Path call in the verification script as
before and run in an Administrator prompt)
On Tue, Jan 7, 2025 at 7:54 PM David Li wrote:
>
> Hello,
>
> I would li
I've created the maint-19.0.0 branch based on
f41f59066b79fbf59719e68ef0f908afd6c5218c and will continue with the
release process from there. Thanks to everyone for tagging and
resolving issues.
[1] https://github.com/apache/arrow/milestone/66
On Wed, Jan 1, 2025 at 1:59 PM Bryce Mecum
] https://github.com/apache/arrow/milestone/66
On Wed, Dec 18, 2024 at 10:08 AM Bryce Mecum wrote:
>
> Hello all,
>
> I'd like to propose a feature freeze date of Monday, January 6th, 2025
> for the upcoming 19.0.0 release of Arrow. Please take a look through
> the mil
; > Hi Bryce,
> >
> > This sounds good to me.
> >
> > Thanks
> >
> > Antoine.
> >
> >
> > Le 18/12/2024 à 19:08, Bryce Mecum a écrit :
> > > Hello all,
> > >
> > > I'd like to propose a feature freeze date of Mond
Hello all,
I'd like to propose a feature freeze date of Monday, January 6th, 2025
for the upcoming 19.0.0 release of Arrow. Please take a look through
the milestone [1] to ensure it includes the issues you expect and to
see if any need your attention. There are currently two issues labeled
as bloc
+1 (non-binding)
Tested on macOS 15.1.1 (aarch64).
On Mon, Dec 2, 2024 at 11:20 PM Sutou Kouhei wrote:
>
> Hi,
>
> I would like to propose the following release candidate (RC1) of
> Apache Arrow Julia version 2.8.0.
>
> This release candidate is based on commit:
> 0d3c98c1bd048f42f3666e040c2f363
, Raúl Cumplido, Sutou Kouhei
> +1 (non binding): Ruoxi Sun, Gang Wu, Bryce Mecum
>
> Bryce will take point on the post release tasks for 18.1.0.
>
>
> Jacob
>
>
> Am Do., 21. Nov. 2024 um 00:23 Uhr schrieb David Li :
> >
> > +1 (binding)
> >
> > Test
Congrats Adam!
On Mon, Nov 18, 2024 at 4:31 PM Sutou Kouhei wrote:
>
> On behalf of the Arrow PMC, I'm happy to announce that Adam Reeve
> has accepted an invitation to become a committer on Apache
> Arrow. Welcome, and thank you for your contributions!
>
> --
> kou
>
+1 (non-binding)
I successfully verified by running:
TEST_DEFAULT=0 \
TEST_CPP=1 \
./dev/release/verify-release-candidate.sh 18.1.0 2
on macOS 15.1 (aarch64). I couldn't verify Python because I was
getting consistent crashes in the Flight tests [1].
[1] https://gist.github.com/amoeba/6eb6
+1 (non-binding)
I successfully verified on macOS 15.1 (aarch64) by running:
DOCKER_DEFAULT_PLATFORM=linux/amd64 \
USE_CONDA=1 \
./dev/release/verify-release-candidate.sh 15 1
PS: I ran into rate limits when downloading artifacts from GitHub.
Dewey pointed me to a recent PR [1] which hel
ample, deciding which PRs should be merged or not with
> discussion, scheduling the next release, starting a vote and
> so on.
>
>
> Thanks,
> --
> kou
>
> In
> "Re: 18.0.1 release manager" on Tue, 5 Nov 2024 10:09:24 -0800,
> Bryce Mecum wrote:
>
>
> > We're still waiting for one or more volunteers for releasemanager.
> Yes makes sense to spread the knowledge!
I'm happy to help even more with the follow-up release but I think I'd
feel most comfortable with someone more familiar with the release
management process to lead this one (Jacob? Kou
> It may be better that the Arrow R package may wait for 18.0.1 (or 18.1.0) if
> we haven't submitted it to CRAN yet.
I think so too. For the R package, we'll wait for 18.0.1/18.1.0 to
submit to CRAN [1].
[1] https://github.com/apache/arrow/issues/44496#issuecomment-2451831654
On Sat, Nov 2, 2
Congrats Curt!
On Wed, Oct 30, 2024 at 2:56 PM Sutou Kouhei wrote:
>
> The Project Management Committee (PMC) for Apache Arrow has
> invited Curt Hagenlocher to become a PMC member and we are
> pleased to announce that Curt Hagenlocher has accepted.
>
> Congratulations and welcome!
Congratulations Neal!
On Wed, Oct 30, 2024 at 4:28 AM Andrew Lamb wrote:
>
> I am pleased to announce that the Arrow Project has a new PMC chair and VP
> as per our tradition of rotating the chair once a year. Andy Grove has
> resigned and
> Neil Richardson was duly elected by the PMC and approve
Congrats, welcome, and thanks for all the great work so far!
On Tue, Oct 22, 2024 at 12:02 PM Weston Pace wrote:
>
> On behalf of the Arrow PMC, I'm happy to announce that Rossi Sun has
> accepted an invitation to become a committer on Apache Arrow. Welcome,
> and thank you for your contributions
+1 (non-binding)
I ran `dev/release/verify-release-candidate.sh 18.0.0 0` on macOS 14.7
(aarch64).
On Fri, Oct 18, 2024 at 3:26 AM Raúl Cumplido wrote:
>
> Hi,
>
> I would like to propose the following release candidate (RC0) of Apache
> Arrow version 18.0.0. This is a release consisting of 327
+1 (non-binding)
I ran `dev/release/verify-release-candidate.sh 53.2.0 1` on macOS 14.7
(aarch64) using the 1.82.0 toolchain.
On Mon, Oct 21, 2024 at 11:27 AM Andrew Lamb wrote:
>
> Hi,
>
> I would like to propose a release of Apache Arrow Rust Implementation,
> version 53.2.0. Note this is ahea
+1 (non-binding)
Verified on macOS 14.7 aarch64
On Wed, Oct 16, 2024 at 12:10 PM Matt Topol wrote:
>
> Hi,
>
> I would like to propose the following release candidate (RC0) of
> Apache Arrow Go version 18.0.0.
>
> This release candidate is based on commit:
> c124ae4449d8cb249bb870cd7a3c533f6ca17
Hi Dewey,
After seeing the test failure Kou reported, I attempted verification
on my x86 debian sid machine and got a Python test failure in
tests/test_iterator.py::test_get_tzinfo. I put the detailed output in
a gist [1]. I can reproduce it outside the verification script.
[1] https://gist.githu
+1 (non-binding)
Verified on macOS 15.0.1 (aarch64) w/ Homebrew
On Tue, Oct 8, 2024 at 8:05 PM Dewey Dunnington
wrote:
>
> Hello,
>
> I would like to propose the following release candidate (rc0) of
> Apache Arrow nanoarrow [0] version 0.6.0. This release consists of 114
> resolved GitHub issues
Congrats Will!
On Tue, Oct 1, 2024 at 9:55 AM Dewey Dunnington
wrote:
>
> On behalf of the Arrow PMC, I'm happy to announce that Will Wyd has
> accepted an invitation to become a committer on Apache Arrow. Welcome,
> and thank you for your contributions!
>
> -dewey
Thanks for driving this forward. I didn't see the links in my email client
so I'm adding those below in case helps others:
Issue: https://github.com/apache/arrow/issues/43495
PR: https://github.com/apache/arrow/pull/43389
On Thu, Aug 1, 2024 at 4:06 AM Ruoxi Sun wrote:
> Hello everyone,
>
> We'
+1 (non-binding)
Verified on:
- macOS aarch64
- Debian 12 x86_64 inside a conda environment (note I had to install
Python 3.11 separately from the instructions, not sure I missed a
step)
On Wed, May 22, 2024 at 10:18 AM Dewey Dunnington
wrote:
>
> Hello,
>
> I would like to propose the followin
Hi Christian, welcome.
Your code looks reasonable to me at first glance. It does seem
possible you're resource-constrained with that t2.micro instance. You
might try using a larger instance or reducing the batch size in your
call to iter_batches [1] to some very small number.
[1]
https://arrow.a
+1 (non-binding)
I ran TEST_DEFAULT=0 TEST_CPP=1
./dev/release/verify-release-candidate.sh 16.1.0 1 on aarch64 macOS
14.4.1 with Homebrew. I did run into one failing test which I've filed
as [1].
[1] https://github.com/apache/arrow/issues/41605
On Thu, May 9, 2024 at 5:05 AM Raúl Cumplido wrote
Congrats Dane!
On Tue, May 7, 2024 at 5:53 AM Joris Van den Bossche
wrote:
>
> On behalf of the Arrow PMC, I'm happy to announce that Dane Pitkin has
> accepted an invitation to become a committer on Apache Arrow. Welcome,
> and thank you for your contributions!
>
> Joris
ocial media platforms have been adopted at this time
and I appreciate all comments others have shared.
Thanks all.
On Sat, Jan 27, 2024 at 1:06 PM Bryce Mecum wrote:
>
> I noticed that the @ApacheArrow Twitter account [1] hasn't posted
> since June 2023 which is around the time of t
Congratulations!
On Thu, Apr 11, 2024 at 3:13 AM Sutou Kouhei wrote:
>
> Hi,
>
> On behalf of the Arrow PMC, I'm happy to announce that Sarah
> Gilmore has accepted an invitation to become a committer on
> Apache Arrow. Welcome, and thank you for your contributions!
>
> Thanks,
> --
> kou
Congrats, Joel!
On Mon, Apr 1, 2024 at 6:59 AM Matt Topol wrote:
>
> On behalf of the Arrow PMC, I'm happy to announce that Joel Lubinitsky has
> accepted an invitation to become a committer on Apache Arrow. Welcome, and
> thank you for your contributions!
>
> --Matt
+1 (non-binding)
Verified on Windows x86_64 with USE_CONDA=1. I ran into two small
issues and filed an issue [1] and sent in a PR containing the changes
I made.
[1] https://github.com/apache/arrow-adbc/issues/1683
On Thu, Mar 28, 2024 at 7:07 AM David Li wrote:
>
> Hello,
>
> I would like to pr
I'd be happy to contribute C# and Ruby examples. I'll work on those this week.
On Tue, Mar 5, 2024 at 7:03 PM Ian Cook wrote:
>
> Update on recent progress in this Arrow-over-HTTP project:
>
> I cleaned up the minimal examples of HTTP clients and servers and
> moved them into a directory in the A
+1 (non-binding)
Verified C++ on Windows 11, VS 2019, conda. I ran into an issue
building PyArrow [1] which I don't think is a problem for release.
[1] https://github.com/apache/arrow/issues/40375
On Mon, Mar 4, 2024 at 12:05 AM Raúl Cumplido wrote:
>
> Hi,
>
> I would like to propose the follo
Hi Andrew, thanks for the question.
Try specifying a schema to `open_dataset` with d1 specified as
date32[day]. When I do that, I get the correct type for that field and
the values look correct too.
schm <- schema(bb)
new_schm <- schm$SetField(6, arrow::field("d1", arrow::date32()))
bb <- arrow::
Hi Sujud. It looks like there was some mention of the reason for not
implementing DoExchange in the PR [1] that created the initial
implementation. I'm not familiar with the code but I hope that helps.
[1] https://github.com/apache/arrow/pull/8694
On Tue, Feb 13, 2024 at 11:59 PM Sujud Abu Atta
n additional platforms,
cross-posting using a tool like Buffer seems like the best option even
if the project doesn't create any new accounts at this time.
On Sat, Jan 27, 2024 at 1:06 PM Bryce Mecum wrote:
>
> I noticed that the @ApacheArrow Twitter account [1] hasn't posted
>
n for terminating the @ApacheArrow account, IMHO.
> >
> > Regards
> >
> > Antoine.
> >
> >
> > Le 27/01/2024 à 23:06, Bryce Mecum a écrit :
> > > I noticed that the @ApacheArrow Twitter account [1] hasn't posted
> > > since June 2023
g the @ApacheArrow account, IMHO.
Thanks for sharing this perspective, Antoine. I suspect you're not
alone in it but, based in part on other responses in this thread so
far, I suspect the community thinks the positives outweigh the
negatives at this point.
>
> Regards
>
> Antoine.
I noticed that the @ApacheArrow Twitter account [1] hasn't posted
since June 2023 which is around the time of the Arrow 12 release. When
I asked on Zulip [2] about who runs or has access to post as that
account, Kou indicated the account was managed using TweetDeck [3] and
that this may no longer b
er listening using
> TLS in the first place.
>
> On Sat, Dec 30, 2023, at 18:57, Bryce Mecum wrote:
> > Hi Rick,
> >
> > You're right that TLS support is built into PyArrow Flight [1]. I
> > think the issue with your code is that your client isn't
Hi Rick,
You're right that TLS support is built into PyArrow Flight [1]. I
think the issue with your code is that your client isn't attempting to
connect over TLS and that the default behavior of the FlightServerBase
must be to allow both TLS and non-TLS connections. This seems to be
similar to ho
Hi Chris, this is very much the place to ask a question like this and
thanks for doing so.
Could we get a little more information on the specific change you were
affected by just so we're all on the same page? Was this the bump from
Parquet 2.4 to 2.6 [1] that happened in the PyArrow 13 release [2
Hi Li, I think what you're after is ColumnReaderImpl::NextBatch [1]
which looks like it eventually calls TransferZeroCopy [2] in the case
of primitive types like float/double (amongst others).
[1]
https://github.com/apache/arrow/blob/main/cpp/src/parquet/arrow/reader.cc#L107
[2]
https://github.c
Congrats, Raúl!
On Mon, Nov 13, 2023 at 10:28 AM Andrew Lamb wrote:
>
> The Project Management Committee (PMC) for Apache Arrow has invited
> Raúl Cumplido to become a PMC member and we are pleased to announce
> that Raúl Cumplido has accepted.
>
> Please join me in congratulating them.
>
> And
Submitting a PR and marking it as a "Draft" would be fine and so would
writing up a design doc and soliciting feedback on this mailing list.
It really depends on what you think would help you the most at this
point. If you submit a draft PR, reply to this email thread with a
link to increase its vi
I've failed to verify this release candidate on macOS M1, running
"dev/release/verify-release-candidate.sh 14.0.0 2" [1]. The failure
looks related to the Go implementation's "parquet-encryption-test".
Can anyone on a similar machine verify?
[1] https://gist.github.com/amoeba/f47534bea44d78a7ee79e
Is the `docker-compose run r` output before or after you changed the
line endings in build_arrow_static.sh? This error:
inst/build_arrow_static.sh: line 38: $'\r': command not found
makes it look like you may have written the file out with
Windows-style line endings which I suspect MinGW is havin
That error makes it look like you're running `docker compose up` from
the root of the Arrow source tree which is likely not what you want.
Are you trying to use the Arrow R package in a Docker container or are
you trying to contribute to it by developing inside of a Docker
container? Nic's link [1]
Congratulations, Jon!
On Sat, Oct 14, 2023 at 9:24 AM Andrew Lamb wrote:
>
> The Project Management Committee (PMC) for Apache Arrow has invited
> Jonathan Keane to become a PMC member and we are pleased to announce
> that Jonathan Keane has accepted.
>
> Congratulations and welcome!
>
> Andrew
+1 (non-binding)
Verified with `./verify-release-candidate.sh 0.3.0 0` on:
- Windows 10, x86_64, libarrow-main, MSVC 17 2022, R 4.3.1, Rtools 43
- macOS 13.6, aarch64, libarrow 13.0.0, R 4.3.1
- Ubuntu 23.04, aarch64, libarrow 13.0.0, R 4.2.2
I'm not aware of one but I'd love to see one get started and would be
happy to contribute.
Related, I'm aware that Nic Crane and Marlene Mhangami have put
together resources in the "awesome-x" style for R [1] and Python [2],
respectively.
[1] https://github.com/thisisnic/awesome-arrow-r
[2] https
Congratulations, Will!
+1 (non-binding)
Verified on:
- Fedora 37 (amd64)
- Debian 11 (amd64)
On Wed, Mar 1, 2023 at 8:04 AM Dewey Dunnington
wrote:
> Hello,
>
> I would like to propose the following release candidate (RC1) of Apache
> Arrow nanoarrow [0] version 0.1.0. This is an initial release consisting of
> 31 r
Hi Shaheer, welcome! I think the mailing list may have had an issue with
your attachment. If the output is short, could you reply with it here? If
it's more than 10-20 lines, you might put it in a Gist [1] or similar type
of pastebin and reply with a link.
[1] https://gist.github.com/
Hi Jean-Luc,
I was able to run your code successfully on my machine but I found it used
considerably more memory (~30GB) and took longer to execute (~30s) than
expected. Could you please file a JIRA ticket [1] and someone can look into
it? The docs have a bug report guide [2] which might be helpfu
96 matches
Mail list logo
