Re: [VOTE] Add RLE Arrays to Arrow Format

+1 I agree that run-end encoding makes more sense but also don't see it as a deal breaker. The most compelling counter-argument I've seen for new types is to avoid a schism where some implementations do not support the newer types. However, for the type proposed here I think the risk is low beca

Re: Request for Patch release of 10.0.2

@Matt. Thanks and I also wish you a good vacation and a good end of the year! --Laurent On Fri, Dec 16, 2022 at 9:31 AM Matt Topol wrote: > @Laurent: I just merged the patches into the "maint-10.0.x" branch. You > should be able to use `go mod edit -replace` to point at that branch > instead of

Re: [VOTE] Add RLE Arrays to Arrow Format

+1 on the proposal as written I think it makes sense and offers exciting opportunities for faster computation (especially for cases where parquet files can be decoded directly into such an array and avoid unpacking. RLE encoded dictionary are quite compelling) I would prefer to use the term Run-E

Re: [DISC] Self-Hosted Runners for Arrow

No news with regards to arrow specific S390x machines but apparently IBM has donated a number of S390x VMs to the ASF which we should be able to use but I have not had the time yet to investigate this option. Matt Topol schrieb am Fr., 16. Dez. 2022, 17:01: > These are awesome! Has there been a

Re: Request for Patch release of 10.0.2

@Laurent: I just merged the patches into the "maint-10.0.x" branch. You should be able to use `go mod edit -replace` to point at that branch instead of the v10.0.1 version tag and pick up the patches. Once v11 is released in mid-January, v11 will also contain these fixes and you'll be able to remo

Re: [VOTE] Disable ASF Jira issue reporting

Raul opened these issues to track required changes to the release scripts: * [Release][Archery] Update archery release curate to support GitHub issues [1] * [Release][Archery] Update archery release changelog to support GitHub issues [2] * [Release][Archery] Update archery release cherry-pick to su

Re: [DISC] Self-Hosted Runners for Arrow

These are awesome! Has there been any luck in reaching out to IBM to see if they could donate one or more s390x VMs to use as runners for testing the s390x builds? That is probably my only concern with Travis going away at EOY, since we don't have a way currently to test those builds on GH Actions.

Re: [VOTE] Disable ASF Jira issue reporting

Thanks for bringing that point up Raul! Would a good workaround be to open the required Jira issues now, before we lock the Jira? On Fri, Dec 16, 2022 at 1:42 PM Raúl Cumplido wrote: > Thanks Rok for looking into this. > > I am ok migrating to GitHub but I want to mention that there are some >

[DISC] Self-Hosted Runners for Arrow

I would like to propose the addition of a self-hosted runner system to the arrow repository to add speciality runners (arm64 and CUDA). This will allow us to compensate for the arm64 jobs that previously ran on Travis, which will be turned off EOY[1]. The migration to GitHub Issues will require a

Re: [VOTE] Disable ASF Jira issue reporting

Thanks Rok for looking into this. I am ok migrating to GitHub but I want to mention that there are some archery related commands like `archery release curate`, `archery release changelog` and more importantly `archery release cherry-pick` that must be updated in order to work with GitHub. For the

Re: [ANNOUNCE] New Arrow committer: Jacob Wujciak

Welcome aboard! On Fri, Dec 16, 2022 at 2:45 AM Ian Joiner wrote: > Congrats Jacob! > > Ian > > On Fri, Dec 16, 2022 at 1:15 AM Nic Crane wrote: > > > On behalf of the Arrow PMC, I'm happy to announce that Jacob Wujciak has > > accepted an invitation to become a committer on Apache Arrow. Welco