+ dev@parquet
On Fri, Jun 16, 2023 at 7:43 AM Jacob Wujciak-Jens
wrote:
> +1 on the update but also on properly communicating the change to avoid
> surprising issues :)
>
> On Thu, Jun 15, 2023 at 7:53 PM Joris Van den Bossche <
> jorisvandenboss...@gmail.com> wrote:
>
> > On Thu, 15 Jun 2023
+1 on the update but also on properly communicating the change to avoid
surprising issues :)
On Thu, Jun 15, 2023 at 7:53 PM Joris Van den Bossche <
jorisvandenboss...@gmail.com> wrote:
> On Thu, 15 Jun 2023 at 19:08, Ian Cook wrote:
> >
> > It will still be possible to write files using
On Thu, 15 Jun 2023 at 19:08, Ian Cook wrote:
>
> It will still be possible to write files using Parquet 2.4 by
> explicitly specifying the 2.4 version to the Parquet writer, correct?
> If yes, that provides a simple workaround for users who encounter
> compatibility issues.
Indeed. Using the
On 2023/06/15 16:24:44 Joris Van den Bossche wrote:
> Hi all,
>
> Bringing up https://github.com/apache/arrow/issues/35746 to the
> mailing list: this issue proposes to bump the default Parquet version
> we use for writing to Parquet files in the C++ library (and in the
> various bindings
It will still be possible to write files using Parquet 2.4 by
explicitly specifying the 2.4 version to the Parquet writer, correct?
If yes, that provides a simple workaround for users who encounter
compatibility issues.
However we should take care to document this as a potentially breaking
Hi all,
Bringing up https://github.com/apache/arrow/issues/35746 to the
mailing list: this issue proposes to bump the default Parquet version
we use for writing to Parquet files in the C++ library (and in the
various bindings including pyarrow and R arrow) from the current
default of "2.4" to
