> INFRA tickets are required before migration.
Perhaps this is different for existing repositories, but just a note
that it may also be possible by editing .asf.yaml (e.g. [1])
[1]
https://github.com/apache/arrow-nanoarrow/blob/81711045e8bb4ded1cb3b5a6fa354b35f18aa4e7/.asf.yaml#L24-L25
On Wed,
Just want to mention that these apache/parquet-* Github repositories
have not yet enabled issues and INFRA tickets are required before
migration.
Best,
Gang
On Thu, May 30, 2024 at 1:55 AM Micah Kornfield
wrote:
> SGTM +1
>
> On Wed, May 29, 2024 at 10:50 AM Rok Mihevc wrote:
>
> > On Wed, May
+1 (binding for Arrow)
In
"[VOTE] Migration of parquet-cpp issues to Arrow's issue tracker" on Wed, 29
May 2024 16:14:44 +0200,
Rok Mihevc wrote:
> # sending this to both dev@arrow and dev@parquet
>
> Hi all,
>
> Following the ML discussion [1] I would like to propose a vote for
> parque
I've noticed that a number of Arrow people will be in Seattle in August. I
know there are a number of Arrow contributors that live in the Seattle area
as well. I'd like to organize a face-to-face meetup for the Arrow
community and have created an issue for discussion[1]. I welcome any
input, fee
SGTM +1
On Wed, May 29, 2024 at 10:50 AM Rok Mihevc wrote:
> On Wed, May 29, 2024 at 4:39 PM Fokko Driesprong wrote:
>
> > Hey Rok,
> >
> > Thanks for bringing this up. I'm also very much in favor of Github. Once
> > we've migrated cpp, I think migrating the other repositories is a great
> > id
On Wed, May 29, 2024 at 4:39 PM Fokko Driesprong wrote:
> Hey Rok,
>
> Thanks for bringing this up. I'm also very much in favor of Github. Once
> we've migrated cpp, I think migrating the other repositories is a great
> idea. Let me know if I can help!
Perfect! A question I think we want to ans
+1 (binding for Arrow and Parquet)
On Wed, May 29, 2024 at 12:13 PM Raúl Cumplido
wrote:
> +1 (binding for Arrow)
>
> El mié, 29 may 2024, 18:15, Andy Grove escribió:
>
> > +1 (binding for Arrow).
> >
> > Thanks,
> >
> > Andy.
> >
> > On Wed, May 29, 2024 at 9:48 AM Alenka Frim > .invalid>
> >
+1 (binding for Arrow)
El mié, 29 may 2024, 18:15, Andy Grove escribió:
> +1 (binding for Arrow).
>
> Thanks,
>
> Andy.
>
> On Wed, May 29, 2024 at 9:48 AM Alenka Frim .invalid>
> wrote:
>
> > +1 (non-binding)
> >
> > Thank you Rok!
> >
> > On Wed, May 29, 2024 at 4:57 PM Gang Wu wrote:
> >
>
All post-release tasks are now complete!
[x] Closed GitHub milestone
[x] Added release to the Apache Reporter System
[x] Uploaded artifacts to Subversion
[x] Created GitHub release
[x] Submit R package to CRAN
[x] Submit Python package to PyPI
[x] Update Python package on conda-forge
[x] Finish re
+1 (binding for Arrow).
Thanks,
Andy.
On Wed, May 29, 2024 at 9:48 AM Alenka Frim
wrote:
> +1 (non-binding)
>
> Thank you Rok!
>
> On Wed, May 29, 2024 at 4:57 PM Gang Wu wrote:
>
> > +1 (binding for Parquet)
> >
> > Thanks!
> > Gang
> >
> > On Wed, May 29, 2024 at 10:47 PM Fokko Driesprong
+1 (non-binding)
Thank you Rok!
On Wed, May 29, 2024 at 4:57 PM Gang Wu wrote:
> +1 (binding for Parquet)
>
> Thanks!
> Gang
>
> On Wed, May 29, 2024 at 10:47 PM Fokko Driesprong
> wrote:
>
> > +1 (non-binding)
> >
> > Op wo 29 mei 2024 om 16:46 schreef Felipe Oliveira Carvalho <
> > felipe...
The Apache Arrow community is pleased to announce the 0.5.0 release of
Apache Arrow nanoarrow. This initial release covers 79 resolved issues
from 9 contributors[1].
The release is available now from [2], release notes are available at
[3], and a blog post highlighting new features and breaking ch
+1 (binding for Parquet)
Thanks!
Gang
On Wed, May 29, 2024 at 10:47 PM Fokko Driesprong wrote:
> +1 (non-binding)
>
> Op wo 29 mei 2024 om 16:46 schreef Felipe Oliveira Carvalho <
> felipe...@gmail.com>:
>
> > +1 (non-binding)
> >
> > On Wed, 29 May 2024 at 11:30 Micah Kornfield
> > wrote:
> >
+1 (non-binding)
Op wo 29 mei 2024 om 16:46 schreef Felipe Oliveira Carvalho <
felipe...@gmail.com>:
> +1 (non-binding)
>
> On Wed, 29 May 2024 at 11:30 Micah Kornfield
> wrote:
>
> > +1 (non-binding for Parquet, Binding for Arrow if that makes a
> difference)
> >
> >
> >
> > On Wed, May 29, 202
+1 (non-binding)
On Wed, 29 May 2024 at 11:30 Micah Kornfield wrote:
> +1 (non-binding for Parquet, Binding for Arrow if that makes a difference)
>
>
>
> On Wed, May 29, 2024 at 7:15 AM Rok Mihevc wrote:
>
> > # sending this to both dev@arrow and dev@parquet
> >
> > Hi all,
> >
> > Following th
Hey Rok,
Thanks for bringing this up. I'm also very much in favor of Github. Once
we've migrated cpp, I think migrating the other repositories is a great
idea. Let me know if I can help!
Kind regards,
Fokko
Op wo 29 mei 2024 om 16:03 schreef Rok Mihevc :
> On Wed, May 29, 2024 at 3:22 AM Gang W
Hi Antoine,
Thank much for the reply! I did create an GitHub issue yesterday.
#41862
On Wed, May 29, 2024 at 10:24 AM Antoine Pitrou wrote:
>
> Hi Li!
>
> Sorry for the delay.
> It seems the problem lies here:
>
> https://github.com/apache/arrow/blob/9f5899019d23b2b1eae2fedb9f6be8827885d843/cp
+1 (non-binding for Parquet, Binding for Arrow if that makes a difference)
On Wed, May 29, 2024 at 7:15 AM Rok Mihevc wrote:
> # sending this to both dev@arrow and dev@parquet
>
> Hi all,
>
> Following the ML discussion [1] I would like to propose a vote for
> parquet-cpp issues to be moved fr
Hi Li!
Sorry for the delay.
It seems the problem lies here:
https://github.com/apache/arrow/blob/9f5899019d23b2b1eae2fedb9f6be8827885d843/cpp/src/arrow/filesystem/s3fs.cc#L1858
The Future is marked finished with the ObjectOutputStream's mutex taken,
and the Future's callback then triggers a c
+1 (binding).
Thanks for taking this up, Rok!
Regards
Antoine.
Le 29/05/2024 à 16:14, Rok Mihevc a écrit :
# sending this to both dev@arrow and dev@parquet
Hi all,
Following the ML discussion [1] I would like to propose a vote for
parquet-cpp issues to be moved from Parquet Jira [2] to Arr
# sending this to both dev@arrow and dev@parquet
Hi all,
Following the ML discussion [1] I would like to propose a vote for
parquet-cpp issues to be moved from Parquet Jira [2] to Arrow's issue
tracker [3].
[1] https://lists.apache.org/thread/zklp0lwcbcsdzgxoxy6wqjwrvt6y4s9p
[2] https://issues.a
On Wed, May 29, 2024 at 3:22 AM Gang Wu wrote:
> Perhaps we can directly proceed to a vote?
>
Since we seem to be in agreement regarding parquet-cpp I'll go ahead and
call for a vote.
I would meanwhile propose to discuss migration of other parquet issues
(parquet-java, parquet-site, parquet-for
Thanks for the quick reply and action Raúl. I'm also very happy to help
craft such a document. I know that the need and use of being on the
ursacomputing org is limited, since the comment bot generally works well,
but it still would be nice to have something like that.
Thank you again!
-Jon
On
Hi,
In preparation for the next major Arrow release (17.0.0) I am planning
on setting the 1st of July, first Monday of July, as the feature
freeze date.
If there are any issues that should block the release please remember
to add the `Priority: blocker` label in the issue on GitHub. There are
cur
24 matches
Mail list logo
