ouhei wrote:
>
> > Sure!
> >
> > In
> > "Re: [DISCUSS] Interest in a 12.0.1 patch?" on Fri, 19 May 2023 11:01:52
> > +0200,
> > Raúl Cumplido wrote:
> >
> > > Hi,
> > >
> > > Based on some conversations, I am +1 on
quot;Re: [DISCUSS] Interest in a 12.0.1 patch?" on Fri, 19 May 2023 11:01:52
> +0200,
> Raúl Cumplido wrote:
>
> > Hi,
> >
> > Based on some conversations, I am +1 on creating the 12.0.1 release. I
> > can work as release manager for the release, I'll need a PMC
Sure!
In
"Re: [DISCUSS] Interest in a 12.0.1 patch?" on Fri, 19 May 2023 11:01:52
+0200,
Raúl Cumplido wrote:
> Hi,
>
> Based on some conversations, I am +1 on creating the 12.0.1 release. I
> can work as release manager for the release, I'll need a PMC to sign
Hi,
Based on some conversations, I am +1 on creating the 12.0.1 release. I
can work as release manager for the release, I'll need a PMC to sign
and upload packages as usual. Kou, will you be able to help me with
that?
Thanks,
Raúl
El jue, 18 may 2023 a las 19:52, Will Jones
() escribió:
>
>
I have two parquet related bug fixes and I wonder if we can release them in
12.0.1
1. https://github.com/apache/arrow/pull/35428
2. https://github.com/apache/arrow/pull/35520
Patch 1 can cause BYTE_STREAM_SPLIT unable to be read if the previous
parquet page is larger than the incoming one.
Patch
Thanks for bringing this up Weston.
Joris has already created a 12.0.1 milestone that contains several fixes
that are candidates for backport [1], including this one. I think this is
the most severe issue though.
As a maintainer of the Python deltalake package, which uses the PyArrow
Parquet
I think it's worthwhile enough to justify the work for the patch. If we do
end up doing the patch, then we should also include this [1] change for the
Go side which, while significant, I didn't believe to be significant enough
to warrant a patch on its own. But it is definitely a good idea to
There is also a major issue with the 12.0.0 R package that has now
been fixed in the repo [2] and needs to be resubmitted to CRAN soon.
The R package developers are supportive of a 12.0.1 patch release
happening soon so that the resubmission of the R package to CRAN can
also include the fix for
