Re: Fwd: [C++] Parquet and Arrow overlap

I have just finished a round of checking parquet-cpp open issues and resolved some of them which I believe are completed. I will start a vote next week. Once the migration is done, what should we do with the Parquet tickets? Now all the Arrow tickets are immutable. However, Parquet tickets should

Re: Fwd: [C++] Parquet and Arrow overlap

> BTW, do we really need to make a full copy of them to have a mirror in the Arrow GitHub issues? I'm assuming we want to move all parquet-cpp issues (open and closed) to Arrow's GitHub issue tracker. The amount of effort required is about the same if we move all or just open tickets. When migrati

Re: Fwd: [C++] Parquet and Arrow overlap

It is great to see some additional enthusiasm and momentum around the Apache Parquet implementation (congratulations on the release of parquet-mr 1.14[1]!). As activity picks up, if the desire is to build more community around Parquet, perhaps the Parquet PMC wants to encourage moving code back to

Re: Fwd: [C++] Parquet and Arrow overlap

I just wanted to also poke the question of non-Java developers who have worked on the other parquet implementations potentially being recognized as committers or otherwise on the Parquet project (speaking as the primary developer of the Go parquet implementation which also lives in the Arrow reposi

Re: Fwd: [C++] Parquet and Arrow overlap

Thank you, that sounds great! On first glance some seem to be rather old and probably don't apply anymore. > BTW, do we really need to make a full copy of them to have a mirror in the Arrow GitHub issues? I am not sure I understand what you mean? A full copy of the open/closed/all issues? I'd say

Re: Fwd: [C++] Parquet and Arrow overlap

I can initiate the vote. But before the vote, I think we need to revisit the states of all unresolved tickets and close some as needed. BTW, do we really need to make a full copy of them to have a mirror in the Arrow GitHub issues? I'd like to seek a consensus here before sending the vote. Best,

Re: [C++] Parquet and Arrow overlap

> > I am a committer on Arrow, > but not on Parquet right now. Does that mean I should only merge Parquet > C++ PRs for code changes in parquet/arrow? FWIW, This was the mode I was operating under. My preference here would be to continue to operate under this mode for the governance perspective.

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: [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: [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: [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 *

Re: [C++] Parquet and Arrow overlap

Hi Will, AFAIK, the Apache Parquet community no longer considers contribution to parquet-cpp when promoting new committers after the donation to Apache Arrow. It would be a dilemma for the parquet-cpp contributors if none of the Apache Arrow community or Apache Parquet community recognizes their

[C++] Parquet and Arrow overlap

Hello, A while back, the Parquet C++ implementation was merged into the Apache Arrow monorepo [1]. As I understand it, this helped the development process immensely. However, I am noticing some governance issues because of it. First, it's not obvious where issues are supposed to be open: In Parqu