Re: [QUESTION][Parquet][Decimal] Why not implement the INT32/INT64 to store Decimal logical type in parquet file

I have created an issue and will work on it: [C++][Parquet] Parquet writer supports writing int32/int64 for decimal type · Issue #15239 · apache/arrow (github.com) Best, Gang On Sat, Jan 7, 2023 at 1:39 AM Micah Kornfield wrote: > > > > Hi Kun, >

Re: Arrow sync call January 4 at 12:00 US/Eastern, 17:00 UTC

On 1/7/23 05:54, Ian Cook wrote: >> If a Google Doc is used, can it be configured to send out notifications of > the summary to the list? > > Not as far as I know, but I think we can continue to send a copy of the > notes to the mailing list after each biweekly meeting, copied and pasted > from th

Re: Arrow sync call January 4 at 12:00 US/Eastern, 17:00 UTC

> If a Google Doc is used, can it be configured to send out notifications of the summary to the list? Not as far as I know, but I think we can continue to send a copy of the notes to the mailing list after each biweekly meeting, copied and pasted from the Google Doc. On Fri, Jan 6, 2023 at 21:40

Re: Arrow sync call January 4 at 12:00 US/Eastern, 17:00 UTC

> Proposal to move sync call meeting notes into a Google Doc > > - Will proposed that we share notes from sync calls in a publicly > viewable Google Doc instead of in emails to the mailing list [2] > - There was a discussion about whether managing edit access to this > Google Doc would be diffic

Re: [Monorepo] Add labels breaking-change and critical-fix

Antoine, I think the challenge is to maintain a shared understanding and definition > of what these terms cover and don't cover. I agree with this. I'd propose that we have a page in our Contributing docs (perhaps the reviewers page?) that defines the criteria for these labels. I can make a PR w

Re: [DISCUSS] State of the Arrow Project 2022

Thanks, Kevin. Documenting a process for determining who should be included on a code > review would be helpful. > That's a good idea. We have a docs page directed at contributors, but I'm not sure how many people have read it [1]. This would be a good addition to it. (There's also a good guide o

Re: [Monorepo] Add labels breaking-change and critical-fix

> To answer Matt's comment, though: those are not necessarily the criteria for minor releases, if we think of the latter as bugfix releases. When we do bugfixes, we release them as Patch releases (which I'd argue is correct). In an ideal world, we'd only do a *major* version release when there are

Re: [Monorepo] Add labels breaking-change and critical-fix

Hey, +1 for the proposal. Perhaps we can loop back and evaluate come 12.0.0 to see if these were useful / used? I'd like to pile on another new label proposal. For purpose of Jira -> GitHub Migration I'd like to propose the following labels be added, that are common on Jira but missing on GitHub:

Re: [DISCUSS] Updating what are considered reference implementations?

I think it would be reasonable to state that a reference implementation must be a complete implementation (i.e. supports all existing types) that is not derived from another implementation (e.g. you can't pick pyarrow and arrow-c++). If an implementation does not plan on ever supporting a new arra

Re: [DISCUSS] State of the Arrow Project 2022

Thank you for starting this discussion, Andrew! Fiona, Sreehari, and I thought a bit about this, and I've summarized some of our thoughts below. Continue: 1. +1 to Will's suggestion about roadmaps for sub-projects. This is something that would be helpful for the MATLAB interface, for example.

Re: Apache Arrow Board Report, by Jan 11 2023

Sreehari, Fiona, and I added a few notes about progress on the MATLAB interface. Best Regards, Kevin Gurney From: Andrew Lamb Sent: Wednesday, January 4, 2023 7:24 PM To: u...@arrow.apache.org ; dev Subject: Re: Apache Arrow Board Report, by Jan 11 2023 Thank y

Re: ADLS C++ support in next release (version 11)

It looks like there is an open PR: https://github.com/apache/arrow/pull/12914 for this but no recent activity. Its not clear how much remaining work there is but it seems like timing might be getting tight. If you need this functionality consider coordinating with the author to see if you can hel

Re: [DISCUSS] Updating what are considered reference implementations?

> > Note this wording talks about "two reference implementations" not "*the* > two reference implementations". So there can be more than two reference > implementations. Maybe reference implementation is the wrong wording here. My main concern is that we try to maintain two "feature complete" im

ADLS C++ support in next release (version 11)

I am curious to know if the ADLS support for the Parquet C++ library will be included in the version 11 release that is scheduled for mid-January (at last check). Does anyone have feedback? We are in need of that capability. Thanks! Jerry

Re: [DISCUSS] Updating what are considered reference implementations?

Le 06/01/2023 à 18:58, Micah Kornfield a écrit : I'm having trouble finding it, but I think we've previously agreed that new features needed implementations in 2 reference implementations before approval (I had thought the community agreed on Java and C++ as the two implementations but I can't

[DISCUSS] Updating what are considered reference implementations?

I'm having trouble finding it, but I think we've previously agreed that new features needed implementations in 2 reference implementations before approval (I had thought the community agreed on Java and C++ as the two implementations but I can't find the vote thread on it). The recent of addition

Re: [Monorepo] Add labels breaking-change and critical-fix

Hello Will, This sounds like a good idea. I think the challenge is to maintain a shared understanding and definition of what these terms cover and don't cover. To answer Matt's comment, though: those are not necessarily the criteria for minor releases, if we think of the latter as bugfix

Re: [QUESTION][Parquet][Decimal] Why not implement the INT32/INT64 to store Decimal logical type in parquet file

> > Hi Kun, > The document of arrow c++ about Reading and writing Parquet files > requires > `(2) On the write side, a FIXED_LENGTH_BYTE_ARRAY is always emitted.` I don't think this is a requirement, it is simply documenting current b

Re: [Monorepo] Add labels breaking-change and critical-fix

I'm extremely in favor of both of these labels for the reasons you state Will. It would be great to see us shift towards being able to do minor releases and not *always* having to do a major version release. --Matt On Fri, Jan 6, 2023 at 12:14 PM Micah Kornfield wrote: > These sounds good to me

Re: [Monorepo] Add labels breaking-change and critical-fix

These sounds good to me, we should be careful around crashes/security issues to not tag them until they are triaged and we decide if a new one-off release is necessary. On Fri, Jan 6, 2023 at 8:57 AM Will Jones wrote: > Hello Arrow devs, > > For the monorepo, I would like to propose adding two n

[Monorepo] Add labels breaking-change and critical-fix

Hello Arrow devs, For the monorepo, I would like to propose adding two new labels to issues: 1. breaking-change: for changes that break API compatibility. 2. critical-fix: for bug fixes that address bugs that are important for users will want to know about, but may not realize affect the