Congratulations!
David Li 于2023年1月12日周四 10:01写道：
> Congrats, Brent!
>
> On Wed, Jan 11, 2023, at 19:07, Jacob Wujciak wrote:
> > Congrats!
> >
> > On Thu, Jan 12, 2023 at 12:06 AM QP Hou wrote:
> >
> >> Congratulations Brent!
> >>
> >> On Wed, Jan 11, 2023 at 2:56 PM Andy Grove
> wrote:
> >>
Congrats, Brent!
On Wed, Jan 11, 2023, at 19:07, Jacob Wujciak wrote:
> Congrats!
>
> On Thu, Jan 12, 2023 at 12:06 AM QP Hou wrote:
>
>> Congratulations Brent!
>>
>> On Wed, Jan 11, 2023 at 2:56 PM Andy Grove wrote:
>>
>> > On behalf of the Arrow PMC, I'm happy to announce that Brent Gardner
>>
Congrats!
On Thu, Jan 12, 2023 at 12:06 AM QP Hou wrote:
> Congratulations Brent!
>
> On Wed, Jan 11, 2023 at 2:56 PM Andy Grove wrote:
>
> > On behalf of the Arrow PMC, I'm happy to announce that Brent Gardner
> > has accepted an invitation to become a committer on Apache
> > Arrow. Welcome, a
Hello Everyone,
As discussed in an issue spawned by the state of the project thread [1] I
have created a draft PR that adds a CODEOWNERS file to apache/arrow [2].
Adding a CODEOWNERS file will allow committers to be automatically
requested for reviews that they are interested in (based on touched
Congratulations Brent!
On Wed, Jan 11, 2023 at 2:56 PM Andy Grove wrote:
> On behalf of the Arrow PMC, I'm happy to announce that Brent Gardner
> has accepted an invitation to become a committer on Apache
> Arrow. Welcome, and thank you for your contributions!
>
> Andy.
>
On behalf of the Arrow PMC, I'm happy to announce that Brent Gardner
has accepted an invitation to become a committer on Apache
Arrow. Welcome, and thank you for your contributions!
Andy.
I saw that a PR related to this issue was merged, but the issue is still
open. I added a comment on the issue asking whether this issue is resolved.
On Mon, Jan 9, 2023 at 11:28 PM Andrew Lamb wrote:
> There is a report[1] of a seemingly serious regression. I recommend we hold
> up finalizing
I think this [1] is the thread where the policy was proposed, but it
doesn't look like we ever settled on "Java and C++" vs. "any two
implementations", or had a vote.
I worry that requiring maintainers to add new format features to two
"complete" implementations will just lead to fragmentation. Pe
Sorry for the double email. "here [1]" should reference
https://github.com/apache/arrow-adbc/milestone/3.
On Wed, Jan 11, 2023, at 14:16, David Li wrote:
> Thanks for bringing this up. My thought is:
>
> - We are treating ADBC's APIs as a specification, so we should vote in
> general.
> - The ch
Thanks for bringing this up. My thought is:
- We are treating ADBC's APIs as a specification, so we should vote in general.
- The changes here are minimal and don't introduce any compatibility concerns -
they just add more constant definitions - so I say we vote and just merge them
into main, in
The Arrow R package dev community call is tomorrow at 17:30 UTC.
Joining instructions are below.
Thursday, 12 January · 17:30 – 18:30
Google Meet joining info
Video call link: https://meet.google.com/dbm-ybmv-evb
Or dial: (ES) +34 910 48 95 10 PIN: 919 955 818 9233#
More phone numbers: https:
Hey all,
I've filed a PR with ADBC (https://github.com/apache/arrow-adbc/pull/316)
to add some more explicitly defined canonical options. This then leads the
an interesting question that should be posed:
For changes like this in general along with other potential updates, should
we do a series of
Sorry, I didn't mean to imply that Flight SQL was Dremio-specific (and indeed
we want to position Flight SQL as a vendor-agnostic protocol). A PR with some
tweaks (and a notice about the correction) would be welcome.
Possibly something like
> ...For example, applications can get Arrow data from
Here is the report that was submitted
## Description:
The mission of Apache Arrow is the creation and maintenance of software
related
to columnar in-memory processing and data interchange
## Issues:
Lack of ASF sponsored invite-free chat service is a minor source of friction
for community buildin
14 matches
Mail list logo
