Adam,
Yes, I saw that when it was introduced here, on a PR I did:
https://github.com/apache/arrow/runs/25894658283
It's on the smallest scale factor and on two of the queries (
https://github.com/voltrondata-labs/arrowbench/blob/main/R/tpch-queries.R#L510-L535
and
https://github.com/voltrondata-la
Congratulations!
On Mon, Mar 18, 2024 at 6:45 AM Rok Mihevc wrote:
> Congrats and welcome Bryce!
>
> On Mon, Mar 18, 2024 at 11:07 AM Andrew Lamb wrote:
>
> > Congratulations Bryce!
> >
> > On Mon, Mar 18, 2024 at 3:35 AM Alenka Frim > .invalid>
> > wrote:
> >
> > > Congratulations Bryce and t
Congratulations!
On Mon, Nov 13, 2023 at 3:10 PM Matt Topol wrote:
> Congratulations Raul!!
>
> On Mon, Nov 13, 2023, 3:09 PM Antoine Pitrou wrote:
>
> >
> > Welcome Raul, we're glad to have you!
> >
> > Regards
> >
> > Antoine.
> >
> >
> > Le 13/11/2023 à 20:27, Andrew Lamb a écrit :
> > > The
Nice work!
Neal
On Thu, Oct 19, 2023 at 4:01 PM Antoine Pitrou wrote:
>
> Hello again,
>
> Quick update: the C++, C#, Go and Java implementations now all
> participate in C Data Interface integration testing.
>
> (this helped us fix a few interoperability bugs, and add deterministic
> releasing
Congratulations!
On Sun, Oct 15, 2023 at 1:35 PM Bryce Mecum wrote:
> 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
Agreed, it's unfortunately not just a simple tradeoff. We have discussed
this a bit in [1] and in several other threads around this topic. If we say
that Arrow is about interchange and not execution, so we shouldn't adopt
the pointer version that DuckDB uses, that means we're also making
interchang
I would be curious how old that language is in the ASF policy. In the era
of cloud infrastructure and public CI, "your own hardware" might mean
something different than it once did. IMO, it is essential that we download
and test the release artifacts in a separate context from where they are
built
+1
Thanks all for the thoughtful discussions here.
Neal
On Fri, Aug 18, 2023 at 4:14 AM Raphael Taylor-Davies
wrote:
> +1 (binding)
>
> Despite my earlier misgivings, I think this will be a valuable addition
> to the specification.
>
> To clarify I've interpreted this as a vote on both Utf8Vie
Hi all,
As was previously raised in [1] and surfaced again in [2], there is a
proposal for representing alternative layouts. The intent, as I understand
it, is to be able to support memory layouts that some (but perhaps not all)
applications of Arrow find valuable, so that these nearly Arrow system
Since this is now the second time that the proposal of a new type has
raised the "alternative layout" question, I'm going to start a new thread
about that.
Neal
On Wed, Jul 12, 2023 at 11:37 AM Pedro Eugenio Rocha Pedreira
wrote:
> Hi all, this is Pedro from the Velox team at Meta. Chiming in h
Thanks, Joe. Looking forward to seeing this come together.
Neal
On Mon, Jul 3, 2023 at 11:29 AM Joe Marshall
wrote:
> Hi,
>
> I'm a pyodide developer amongst other things (webassembly cpython
> intepreter) and I've got some PRs in progress on arrow relating to
> webassembly support. I wondered
Hi all, checking back in about the patch release. Do we have a timeline for
when we plan to do it? Looks like Weston's PR is about ready to go, and I
believe that was the last outstanding issue.
Neal
On Fri, May 19, 2023 at 5:30 AM Sutou Kouhei wrote:
> Sure!
>
> In
> "Re: [DISCUSS] Interest
Congratulations!
On Wed, May 3, 2023 at 1:58 PM Jacob Wujciak
wrote:
> Congratulations, well deserved!
>
> On Wed, May 3, 2023 at 7:48 PM Weston Pace wrote:
>
> > Congratulations!
> >
> > On Wed, May 3, 2023 at 10:47 AM Raúl Cumplido
> > wrote:
> >
> > > Congratulations Matt!
> > >
> > > El mi
Thanks for following up on this. Just a point of order: I don't think PMC
approval or voting is required to merge to arrow-site. Though I agree that
it's always good to get more eyes on things we publish to the web.
Neal
On Fri, Apr 28, 2023 at 6:33 PM Will Jones wrote:
> Thanks for highlightin
+1, thanks for taking the initiative on this!
Neal
On Mon, Apr 24, 2023 at 6:10 AM Andrew Lamb wrote:
> +1
>
>
> On Mon, Apr 24, 2023 at 1:55 AM David Li wrote:
>
> > +1
> >
> > Thanks Kou!
> >
> > On Mon, Apr 24, 2023, at 11:53, Sutou Kouhei wrote:
> > > +1
> > >
> > > In <20230424.103259.664
+1 (Intel Mac)
Neal
On Wed, Apr 19, 2023 at 1:20 PM Jacob Quinn wrote:
> +1 (macOS M1)
>
> -Jacob
>
> On Tue, Apr 18, 2023 at 1:59 AM Sutou Kouhei wrote:
>
> > Hi,
> >
> > I would like to propose the following release candidate (RC1) of
> > Apache Arrow Julia version 2.5.2.
> >
> > This releas
Or, possibly you're on an older version of R, and CRAN no longer builds
binary packages for your version.
Regardless, CRAN doesn't host binary packages for Linux, and we have no
control over what binaries/versions they do host, so unfortunately there's
nothing the Arrow community can do about what
Congrats, Will!
On Mon, Mar 13, 2023 at 2:37 PM Anja wrote:
> Congrats, Will!! =)
>
> On Mon, 13 Mar 2023 at 11:23, Weston Pace wrote:
>
> > Congratulations Will!
> >
> > On Mon, Mar 13, 2023, 11:22 AM Ian Cook wrote:
> >
> > > Congratulations Will!
> > >
> > > On Mon, Mar 13, 2023 at 1:58 PM
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
+1, with or without description
Neal
On Tue, Jan 31, 2023 at 11:04 AM Weston Pace wrote:
> +1 to both. This only applies to the merge button and, in that case, the
> committer has a chance to review the message before merging. So if there
> is garbage in the description hopefully they can cat
> > * Proceed with RC0, fix for 12.0.0 (and 11.0.1, should it happen),
> > and
> > >> > > cherry-pick the fix into the bundle we upload to CRAN for 11.0.0.
> > (This
> > >> > is
> > >> > > something we do regularly, not a cr
Correct, it does. So as long as you base your branch off of the original
contributor's PR, or cherry-pick their commit(s) into yours, the
attribution should show up.
Neal
On Wed, Jan 25, 2023 at 10:54 AM Antoine Pitrou wrote:
>
> Le 25/01/2023 à 16:47, Julian Hyde a écrit :
> > A common practic
I received an email this morning from the CRAN maintainers about a C++
build failure on clang 16. Although clang 16 is not scheduled for release
until March, CRAN wants to ensure that all packages build successfully on
it when it becomes available, so they've given us an ultimatum to fix the
issue
Congratulations!
On Mon, Dec 26, 2022 at 4:38 PM Matt Topol wrote:
> Congrats!!!
>
> On Mon, Dec 26, 2022, 12:47 PM Jacob Wujciak >
> wrote:
>
> > Congratulations Andrew!
> >
> > Matthew Turner schrieb am Mo., 26. Dez.
> > 2022, 16:44:
> >
> > > Congratulations, Andrew!
> > >
> > > From: Yijie
Congrats!
On Thu, Dec 15, 2022 at 7:00 PM Ian Cook wrote:
> Herzlichen Glückwunsch, Jacob!
>
> On Thu, Dec 15, 2022 at 6:56 PM Rok Mihevc wrote:
> >
> > Congrats Jacob!!
> >
> > Rok
> >
> > On Fri, Dec 16, 2022 at 12:52 AM Vibhatha Abeykoon
> > wrote:
> >
> > > Congratulations Jacob!!!
> > >
>
I don't see a problem cherry-picking commits to the maintenance
branch--seems like that's what it should be for, right?
Neal
On Thu, Dec 15, 2022 at 11:17 AM Matt Topol wrote:
> @Kou It looks like we're going to just have a branch as an un-official
> patched version that can solve Laurent's iss
Congratulations!
> On Dec 6, 2022, at 6:11 AM, vin jake wrote:
>
> Congratulations Raúl !!
>
>> On Tue, Dec 6, 2022 at 7:11 PM Rok Mihevc wrote:
>>
>> Congrats Raul!!
>>
>>> On Tue, Dec 6, 2022 at 12:04 PM Andrew Lamb wrote:
>>>
>>> Congratulations Raúl
>>>
>>> On Tue, Dec 6, 2022 at 2
ASF Infra is running a survey and would like feedback from any committer.
Cross-posting here in case folks aren't on the infra mailing list. If you
have opinions you would like to share, please see the link below.
Neal
-- Forwarded message -
From: Chris Thistlethwaite
Date: Thu,
> - This creates an immediate need to modify the PR merge script; Raúl
> opened an issue for this after the call [6]; this also raises the
> question of whether we still need the PR merge script or whether
> committers can use the "Squash and merge" button in the GitHub web UI
> instead
>
I think
+1
Verified on Intel macOS 13
Neal
On Thu, Nov 17, 2022 at 9:00 AM Raúl Cumplido
wrote:
> +1
>
> Tested on Ubuntu 22.04.1 LTS
>
> El jue, 17 nov 2022 a las 14:42, David Li ()
> escribió:
>
> > +1 (binding)
> >
> > Tested on AMD64/Linux (Ubuntu 18.04)
> >
> > On Thu, Nov 17, 2022, at 07:18, Eri
Would it be feasible to make it arrow.apache.org/docs/adbc, and nightly
under arrow.apache.org/docs/dev/adbc, for consistency with the rest of the
docs?
Neal
On Tue, Nov 8, 2022 at 8:27 AM David Li wrote:
> Thanks! Yes, I was looking at how the Cookbook works and plan to use the
> same setup. I
Two unrelated thoughts:
1. Since it sounds like we need to do a patch release for the wheels,
should we include any other critical bugfixes that have been reported
affecting 10.0.0? Do we have a 10.0.1 Fix Version in Jira already, and/or
any known issues we would want to include?
2. Since I said "
n Thu, Oct 27, 2022 at 4:25 PM Matt Topol wrote:
> +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:
> > >
&
t; Arrow Jira issues but never created an Arrow PR that was merged.
> >
> > Please do some sanity-checking on this list before using it.
> >
> > [1] https://gist.github.com/ianmcook/0f1538ebc8268a88cd4e0a0a61445287
> > [2]
> https://docs.google.com/spreadsheets/d/1C8Px
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
Attendees:
Vibhatha Abeykoon
Raúl Cumplido
James Duong
Sean Gallagher
Ian Joiner
Will Jones
David Li
Antoine Pitrou
Neal Richardson
Matt Topol
Jacob Wujciak
Discussion:
Release 10.0.0: it's done, and it seemed to go smoothly. Kudos to all who
have been working to make releases easier!
to create an issue to track a decision/concern
> that's not already defined.
>
> On Tue, Oct 25, 2022 at 6:37 AM Neal Richardson <
> neal.p.richard...@gmail.com>
> wrote:
>
> > I'll start a vote on this in the next day or so since it seems like we
> have
&
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 JI
+1
On macOS 12.6 (arm64), Python 3.9.12, I ran:
TEST_DEFAULT=0 TEST_WHEELS=1 dev/release/verify-release-candidate.sh
10.0.0
and it succeeded, but some Python subprocess or something crashed in the
test suite--I think it was around test_pandas or test_plasma but I wasn't
paying close attentio
I'll start a vote on this in the next day or so since it seems like we have
consensus on the main issue (moving from Jira to GitHub Issues) and are
working out the finer points on how we'll migrate and how we'll map Jira
concepts to Issues.
Speaking of the migration: now would be an *excellent* ti
t;
> Hi Neal,
>
> Le 22/10/2022 à 15:35, Neal Richardson a écrit :
> >
> > Their email says:
> >
> >> Infra knows this process change places an increasing burden on PMC
> members
> >> for managing contributors, and makes it harder for people to con
Hi all,
ASF Infra has announced [1] that, due to spam account creation, it will no
longer be possible for people to sign themselves up for a Jira account to
report issues as of November 6. Instead, the PMC will have to request the
creation of Jira accounts.
Their email says:
> Infra knows this pr
On Thu, Oct 20, 2022 at 11:31 AM Jacob Wujciak
wrote:
> This is definitively an important topic that should be discussed. I just
> want to point out that there is no difference between a major, minor or
> patch release with regards to the ASF process. Any official release needs a
> vote and a PMC
+1
(I think this makes 4 binding +1s, if I count correctly)
On Wed, Oct 5, 2022 at 11:30 AM Antoine Pitrou wrote:
>
> +1 (binding), with the caveat that I looked mostly at the C API.
>
> Regards
>
> Antoine.
>
>
> Le 21/09/2022 à 17:40, David Li a écrit :
> > Hello,
> >
> > We have been discuss
On Mon, Sep 12, 2022 at 12:44 PM David Li wrote:
> I like this idea. I would also like to set up some sort of automated ABI
> checker as well (the options I found were GPL/LGPL so I need to figure out
> how to proceed).
>
You should be able to use GPL software in CI, that's no problem. You can
e
+1
Neal
On Thu, Sep 8, 2022 at 2:15 PM Ashish wrote:
> +1 (non-binding)
>
> On Thu, Sep 8, 2022 at 9:41 AM Gavin Ray wrote:
>
> > Oh, so that's what "non-binding" means in vote threads
> > Those threads make a lot more sense now, thanks for the heads-up =)
> >
> > On Thu, Sep 8, 2022 at 12:31
I agree with Micah. Moreover, adding "org.apache" does not disambiguate
anything; "arrow" should be the reserved namespace for canonical
(extension) types.
Neal
On Wed, Aug 24, 2022 at 12:31 PM Micah Kornfield
wrote:
> Sorry for beling late. I'm -0.5 on "org.apache.arrow." given people
> previ
https://cpp11.r-lib.org/articles/motivations.html is a good summary of why
we use cpp11.
Neal
On Fri, Aug 19, 2022 at 1:23 PM Mauricio Vargas Sepúlveda
wrote:
> Hi!
>
> Which was the practical reason to use cpp11 for the R package?
>
> I ask because now I'm in the process of creating a fork of
I have no opinion about the benefits of upgrading to C++17. From the R
perspective, there are a handful of packages on CRAN that require C++14 or
C++17. Last year, when I asked other R package maintainers why they hadn't
upgraded to newer C++ standards, the reasoning was that because many
packages
+1, SGTM
Neal
On Wed, Aug 10, 2022 at 6:17 PM Rok Mihevc wrote:
> It would be great if this friction point is removed. +1
>
> Rok
>
> On Wed, Aug 10, 2022 at 11:36 PM Sutou Kouhei wrote:
>
> > +1
> >
> > In
> > "Proposal: Allow any ASF Jira user to assign ARROW issues" on Wed, 10
> > Aug 20
CRAN is closed for new submissions until August 5, so I'll submit the R
package next week.
On Wed, Aug 3, 2022 at 7:19 AM Krisztián Szűcs
wrote:
> Below is the current status of the post release tasks, I
> "soft-assigned" a couple of them to the relevant maintainers, could
> you please help with
Sounds good to me too. +1 on the canonical extension type option; maybe it
should end up as a first-class type, but I'd like to see us try it without
first and see what that tells us about the path for having an extension
type get promoted to being a first-class type. This is something that has
bee
ng the link to
> >> the previous discussion and creating the umbrella issue/breaking
> >> down the tasks in Jira.
> >>
> >> I am happy to work on these subtasks to move the effort forward;
> >> I’ll start with this subtask [1].
> >>
> >>
+1
Neal
On Thu, Jul 14, 2022 at 5:17 PM Sutou Kouhei wrote:
> +1
>
> I ran the followings on Debian GNU/Linux sid:
>
> * TEST_DEFAULT=0 \
> TEST_GO=1 \
> dev/release/verify-release-candidate.sh 8.0.1 0
>
> with:
>
> * go version go1.18.3 linux/amd64
>
>
> Thanks,
> --
> kou
>
>
+1
Neal
On Thu, Jul 14, 2022 at 5:16 PM Sutou Kouhei wrote:
> +1
>
> I ran the followings on Debian GNU/Linux sid:
>
> * TEST_DEFAULT=0 \
> TEST_GO=1 \
> dev/release/verify-release-candidate.sh 7.0.1 0
>
> with:
>
> * go version go1.17.11 linux/amd64
>
>
> Thanks,
> --
> kou
>
>
+1. Thank you for doing this, Kou.
Neal
On Thu, Jul 14, 2022 at 5:15 PM Sutou Kouhei wrote:
> +1
>
> I ran the followings on Debian GNU/Linux sid:
>
> * TEST_DEFAULT=0 \
> TEST_GO=1 \
> dev/release/verify-release-candidate.sh 6.0.2 0
>
> with:
>
> * go version go1.18.3 linux/amd
Sounds like a good idea to me, thanks for taking the initiative on this.
To Benson's idea about varying the timeout based on priority, IMO we could
just start with the simple approach and see how that goes. Maybe that would
be helpful but maybe it's not necessary. If you're truly watching an issue
I've enabled the web-public option on https://ursalabs.zulipchat.com/
turned it on for the main discussion streams. Anyone can go to that URL and
not only view discussions in those streams but also sign themselves up to
be able to participate in discussions there.
Neal
On Wed, Jun 29, 2022 at 5:0
One challenge with automatically creating issues is that sometimes a single
cause will make many builds fail (think python wheels or conda packages,
across versions and platforms). So it may end up creating a lot of issues
we have to close as duplicate (and have to track that so we don't re-create
On behalf of the Arrow PMC, I'm happy to announce that
Dewey Dunnington
Alenka Frim
Rok Mihevc
have all accepted invitations to become committers on Apache Arrow!
Welcome, thank you for all your contributions so far, and we look forward
to continuing to drive Apache Arrow forward to an even bette
Personally, I don't have a problem with doing `git tag` just for Go. I
don't think this needs a full patch release process since we aren't
producing new artifacts that need signing, we're only adding a tag that
points to a SHA in git. But I am not an expert in this area of policy and
will defer to
+1
On Wed, Jun 8, 2022 at 7:44 PM Sutou Kouhei wrote:
> +1
>
> In
> "[VOTE] Mark C Stream Interface as Stable" on Wed, 8 Jun 2022 11:15:29
> -0700,
> Will Jones wrote:
>
> > Hi,
> >
> > Given all feedback to discussion [1] has been positive, I would like to
> > propose marking the C Stream
If you have fixes already for building it, perhaps merge those and then
remove it? That way, if we decided that we wanted to restore it (not that I
expect we would), we would be reverting to something that at least built
successfully.
Neal
On Mon, Jun 6, 2022 at 1:04 PM Micah Kornfield
wrote:
Would it make sense to make a draft PR with your branch so that folks can
comment on specific parts of it?
Neal
On Wed, Jun 1, 2022 at 10:20 AM Tobias Zagorni
wrote:
> Am Dienstag, dem 31.05.2022 um 12:41 -0700 schrieb Micah Kornfield:
> >
> > - Should we allow multiple runs of the same value f
+1 from me too to mark it as stable. De facto it is stable: there have been
no modifications to
https://github.com/apache/arrow/blob/master/cpp/src/arrow/c/abi.h since the
stream was added in 2020.
Neal
On Thu, May 26, 2022 at 12:32 PM Dewey Dunnington
wrote:
> I'm fairly new to this but have w
+1
On Tue, May 17, 2022 at 12:46 PM Andrew Lamb wrote:
> +1 (binding)
>
> On Mon, May 16, 2022 at 9:56 AM Andy Grove wrote:
>
> > I would like to propose that we move the Ballista project to a new
> > top-level *arrow-ballista* repository.
> >
> > The rationale for this (copied from the GitHub
ibs-only-l --static --silence-errors ${PKG_CONFIG_NAME}`"
> PKG_LIBS="$PKG_LIBS `PKG_CONFIG_PATH=${LIB_DIR}/pkgconfig pkg-config
> --libs-only-other --static --silence-errors ${PKG_CONFIG_NAME}`"
>
>
> Thanks,
> --
> kou
>
> In
> "Re: [R] Insta
old release candidates
> >
> > On Sat, May 7, 2022 at 3:40 AM Neal Richardson
> > wrote:
> >>
> >> I will handle the R submission to CRAN.
> >>
> >> Neal
> >>
> >> On Fri, May 6, 2022 at 6:14 PM Sutou Kouhei wrot
I will handle the R submission to CRAN.
Neal
On Fri, May 6, 2022 at 6:14 PM Sutou Kouhei wrote:
> > 9. [todo:kou?] upload RubyGems
>
> I'll do it once Homebrew and MSYS2 packages are updated.
>
> In
> "Re: [RESULT][VOTE] Release Apache Arrow 8.0.0 - RC3" on Fri, 6 May 2022
> 23:37:58 +0200,
Hmm, I see a couple of things:
* There are two errors at the end, one about pthread_cancel and one about
undefined symbols for snappy. I can't tell if the pthread issue is fatal.
* On the latter, I see that we're using snappy and lz4 from the system
(cmake finds them in the Arrow C++ build) but wh
I've just given you all the permissions. If you need to manage anything
else in the future, you can click "Space tools" at the bottom left.
Neal
On Thu, Apr 21, 2022 at 3:07 PM Andrew Lamb wrote:
> I would like to be able to contribute to pages in the ARROW confluence
> space, but I don't see a
I failed to verify this on macOS 11.6 arm64. 3 integration tests crashed
with "ArgumentError: unsafe_wrap: pointer 0x13b640ef8 is not properly
aligned to 16 bytes".
I don't know enough to know whether this is a problem with the integration
test setup (and thus probably not release blocking) or whe
Can you file a jira for INFRA? They're the owners of the org (according to
https://github.com/orgs/apache/people?query=role%3Aowner).
Neal
On Tue, Mar 1, 2022 at 9:41 AM Dominik Moritz wrote:
> Hi All,
>
> I got in touch with NPM to see whether we can get the arrow package name on
> NPM (right
Congratulations!
Neal
On Thu, Feb 17, 2022 at 4:48 PM Rok Mihevc wrote:
> Congrats QP!
>
> Rok
>
> On Thu, Feb 17, 2022 at 10:41 PM David Li wrote:
> >
> > Congrats QP!
> >
> > On Thu, Feb 17, 2022, at 16:26, Matthew Turner wrote:
> > > Congratulations, QP! Appreciate all of your contributions
le to ask
INFRA to make the change. Those who are interested in seeing this happen
can work on those subtasks, and we can check back once those are done.
Neal
[1]: https://issues.apache.org/jira/browse/ARROW-15689
On Mon, Feb 14, 2022 at 3:46 PM Antoine Pitrou wrote:
>
> Le 14/02/2022 à
There was discussion of this back in 2020 [1], and the consensus at the
time seemed to be to wait and see where git and GitHub would land before
making what could be a disruptive change. I support reopening the
discussion.
It looks like quite a few ASF projects have switched to 'main' by now [2],
I will handle the R package submission to CRAN.
Neal
On Thu, Feb 3, 2022 at 4:11 PM Sutou Kouhei wrote:
> Hi,
>
> I'll update/upload Homebrew, MSYS2 and RubyGems.
>
> 1. [done] make the released version as "RELEASED" on JIRA
> 2. [done] start the new version on JIRA
> 4. [done] upload source
>
I like the idea too. If we were to use the github action to send tweets, we
would need to get INFRA to add it to the allowlist since they restrict
which actions we can use. I don't think it's a blocker, just would add some
extra time in the process of getting it set up.
Neal
On Tue, Feb 1, 2022
Congratulations!
Neal
On Tue, Jan 25, 2022 at 12:53 PM Benson Muite
wrote:
> Congratulations Kou!
> On 1/25/22 8:44 PM, Vibhatha Abeykoon wrote:
> > Congrats Kou!
> >
> >
> > On Tue, Jan 25, 2022 at 11:13 PM Ian Joiner
> wrote:
> >
> >> Congrats Kou!
> >>
> >> On Tuesday, January 25, 2022, Wes
+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.
>
> An
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 contribution
> I think in this particular case, we should consider the C ABI /
> in-memory representation and IPC format as separate beasts. If an
> implementation of Arrow does not want to use this string-view array
> type at all (for example, if it created memory safety issues in Rust),
> then it can choose t
+1
Ran the verification script on aarch64-apple-darwin.
Neal
On Mon, Dec 13, 2021 at 12:09 AM Benson Muite
wrote:
> +1 non binding. Ran script on Rocky Linux 8.
>
> Steps:
> dnf -y update
> dnf -y install gcc tar git
> git clone https://github.com/apache/arrow-rs
> cd arrow-rs/dev/release
> ba
+1
Ran the verification script on aarch64-apple-darwin.
Neal
On Mon, Nov 29, 2021 at 4:15 PM Andrew Lamb wrote:
> I plan to release this version as soon as we get one more binding (PMC)
> vote. Thank you all for your patience
>
> Andrew
>
> On Sun, Nov 28, 2021 at 11:20 AM Andy Grove wrote:
>
The R package has been submitted to CRAN, currently awaiting approval.
Neal
On Thu, Nov 18, 2021 at 5:35 PM Ian Cook wrote:
> Regarding vcpkg: The 6.0.0 arrow port update PR
> (https://github.com/microsoft/vcpkg/pull/21113) is not yet merged
> because of a problem with the aws-sdk-cpp vcpkg po
Congratulations, Joris!
Neal
On Wed, Nov 17, 2021 at 7:02 PM Keith Kraus wrote:
> Congrats Joris!
>
> On Wed, Nov 17, 2021 at 6:35 PM Weston Pace wrote:
>
> > Congratulations! I continue to be grateful for Joris' many contributions
> > and advice. This is great news.
> >
> > On Wed, Nov 17,
+1
I triggered additional checks on the RC branch (
https://github.com/apache/arrow/pull/11671#issuecomment-969186937) and the
various sanitizers and other checks that simulate CRAN all passed.
Neal
On Sun, Nov 14, 2021 at 9:37 PM Sutou Kouhei wrote:
> Hi,
>
> Unfortunately, it's too late for
+1
Ran the verification script on aarch64-apple-darwin.
Neal
On Fri, Nov 12, 2021 at 9:12 AM Andy Grove wrote:
> +1 (binding)
>
> I did run into a small issue with the release verification script (which I
> ran from the tarball in [2]). After the dry run publishing the arrow crate
> it moved o
I think we should include that fix. On the R side we discovered that people
were relying on the old behavior.
If we're going to cut a new RC it would be good to include a few other
fixes for segfaults that have been discovered:
* https://issues.apache.org/jira/browse/ARROW-14519 (merged)
* https:
Not expressing an opinion on the original question, but if the problem is
"not getting everything right the first time", what can be done to reduce
the likelihood of getting things wrong? Other languages/implementations
have extensive CI and nightly builds, some of which test different
packaging sc
+1
Ran the verification script on aarch64-apple-darwin.
Neal
On Wed, Nov 3, 2021 at 2:29 PM Andrew Lamb wrote:
> Does anyone from the PMC have time to weigh in on the 6.1.0 Rust Arrow
> release candidate? I would like to either release it, or decide we
> shouldn't.
>
> It is currently in a lim
R package has been accepted by CRAN, though we will have to patch and
resubmit due to a sanitizer error (
https://issues.apache.org/jira/browse/ARROW-14514 for the failure,
https://issues.apache.org/jira/browse/ARROW-14515 for the missing CI--we
test UBSAN with gcc but apparently CRAN also does UBS
gt; http://npm.github.io/publishing-pkgs-docs/updating/using-tags.html
>
> On Oct 27, 2021 at 20:58:42, Neal Richardson
> wrote:
>
> > Looking ahead, is there anything we can add to CI and/or release
> > verification to catch things like this before the release?
> >
> > Th
Looking ahead, is there anything we can add to CI and/or release
verification to catch things like this before the release?
There already is a 6.0.1 fix version in Jira so please tag any issues
accordingly.
Neal
On Wed, Oct 27, 2021 at 7:07 PM Matthew Topol wrote:
> There was also an issue fou
+1 from me too. More and more developers seem to be accustomed to using
GitHub Issues to ask for help, and redirecting them to a mailing list adds
a barrier to participation.
Neal
On Wed, Sep 29, 2021 at 2:32 PM Phillip Cloud wrote:
> I am +1 on steering users towards GitHub issues for support
Attendees:
Phillip Cloud
Alenka Frim
Jörn Horstman
Jonathan Keane
Micah Kornfield
Rok Mihevc
Benson Muite
Jacques Nadeau
Eduardo Manuel Ponce Mojica
Weston Pace
Neal Richardson
Joris Van den Bossche
Discussion:
* C++ query engine update (see previous mailing list message)
* 6.0 release is
Hi all,
I wanted to give an update on work that several of us have been doing in
recent months on query processing in C++. Back in March, we circulated [1]
a document [2] with a proposal on implementing the basic pieces of a query
execution engine. Recent patches have introduced some key aspects of
+1 (binding)
Neal
On Mon, Sep 27, 2021 at 6:54 AM Andrew Lamb wrote:
> +1 (binding)
>
> On Mon, Sep 27, 2021 at 12:17 AM Andy Grove wrote:
>
> > +1 (binding)
> >
> > On Sun, Sep 26, 2021 at 9:11 PM Benjamin Kietzman
> > wrote:
> >
> > > +1 (binding)
> > >
> > > On Sun, Sep 26, 2021, 23:08 Mic
people from
> > upgrading from Arrow 3.
> >
> > On Jul 30, 2021 at 14:31:59, Neal Richardson <
> neal.p.richard...@gmail.com>
> > wrote:
> >
> >> Let's give it a few more days to see what other issues come up as more
> >> people install 5
On behalf of the Apache Arrow PMC, I'm happy to announce that Nic Crane
has accepted an invitation to become a committer on Apache Arrow.
Welcome and thank you for your contributions!
Neal
1 - 100 of 800 matches
Mail list logo
