You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@parquet.apache.org by Gang Wu <us...@gmail.com> on 2026/05/28 15:59:44 UTC

[DISCUSS] Release parquet-format 2.13.0?

Hi all,

I would like to start a discussion about a parquet-format 2.13.0 release.

It has been about 9 months since 2.12.0 was released on August 28, 2025.

Since then, we have had some meaningful updates, especially:

- [PR #514](https://github.com/apache/parquet-format/pull/514)
PARQUET-2249: Introduce IEEE 754 total order & NaN-counts
- [PR #565](https://github.com/apache/parquet-format/pull/565) GH-506:
Clarify field ordering for partially shredded object union
- [PR #560](https://github.com/apache/parquet-format/pull/560) Update
wording in Geospatial spec
- [PR #562](https://github.com/apache/parquet-format/pull/562) GH-561:
variant schema examples to use `(VARIANT(1))`

There are also some open PRs that may be worth waiting for, especially:

- [PR #564](https://github.com/apache/parquet-format/pull/564) GH-563:
Make `ColumnMetaData.path_in_schema` optional

It looks promising to me, and there is already related implementation
work in arrow-rs, parquet-java, and arrow-cpp. (Thanks Ed!)

What do people think?

Thanks,
Gang

Re: [DISCUSS] Release parquet-format 2.13.0?

Posted by Gang Wu <us...@gmail.com>.

Bumping this again to call for PMC members to vote on
https://lists.apache.org/thread/7kjqsz7n8cwqpgfo2h9c5q0csml77d86

Or do we need to abort this vote until we sort out approaches for defining
a better Parquet version (preset)?

On Tue, Jun 9, 2026 at 12:33 PM Gang Wu <us...@gmail.com> wrote:

> Vote thread is sent:
> https://lists.apache.org/thread/7kjqsz7n8cwqpgfo2h9c5q0csml77d86
>
> On Mon, Jun 8, 2026 at 10:28 PM Micah Kornfield <em...@gmail.com>
> wrote:
>
>> I also think it is reasonable to start a release.
>>
>> Thanks,
>> Micah
>>
>> On Friday, June 5, 2026, Fokko Driesprong <fo...@apache.org> wrote:
>>
>> > Sounds good, Gang. No objections from my end. Thanks for running this!
>> >
>> > Kind regards,
>> > Fokko
>> >
>> > On 2026/06/05 03:23:55 Gang Wu wrote:
>> > > It seems that the work on making `ColumnMetaData.path_in_schema`
>> > optional
>> > > still needs more discussion as per [1], so I'm inclined not to wait
>> for
>> > it
>> > > for the 2.13.0 release.
>> > >
>> > > Regarding Ismaël's comment [2], I don't think it changes any spec, so
>> it
>> > > should not block the release and reviewers need more time to read
>> them.
>> > >
>> > > If there are no objections, I will create a Release Candidate (RC)
>> next
>> > > week.
>> > >
>> > > [1] https://lists.apache.org/thread/gm7btrgvprdbrh8c5nv061f402txo0vt
>> > > [2] https://github.com/apache/parquet-format/pull/572
>> > >
>> > > Best,
>> > > Gang
>> > >
>> > > On Tue, Jun 2, 2026 at 11:38 PM Ismaël Mejía <ie...@gmail.com>
>> wrote:
>> > >
>> > > > I just wanted to mention that, as part of my ongoing AI
>> explorations, I
>> > > > opened a PR fixing minor issues such as orthography, grammar, and
>> some
>> > > > snippet errors.
>> > > >
>> > > > It’s a small PR (~200 lines), so it should be quick to review and,
>> > > > hopefully, make it into the next release.
>> > > > https://github.com/apache/parquet-format/pull/572
>> > > >
>> > > > Best,
>> > > > Ismaël
>> > > >
>> > > > On Fri, May 29, 2026 at 11:06 AM Fokko Driesprong <fokko@apache.org
>> >
>> > > > wrote:
>> > > >
>> > > > > +1 for the release
>> > > > >
>> > > > > I got a small one to bump to the latest version of Thrift to
>> supress
>> > a
>> > > > > CVE: https://github.com/apache/parquet-format/pull/570
>> > > > >
>> > > > > I don't think we should block releases for format since they are
>> > pretty
>> > > > > ligthtweight and might unblock downstream consumers.
>> > > > >
>> > > > > Thanks,
>> > > > > Fokko
>> > > > >
>> > > > > On 2026/05/29 02:40:14 Micah Kornfield wrote:
>> > > > > > I need to do another pass on the C++ implementation.  I think I
>> saw
>> > > > some
>> > > > > > other comments on the spec change, which I'm not sure if they
>> are
>> > > > > > addressed.
>> > > > > >
>> > > > > > On Thu, May 28, 2026 at 7:07 PM Gang Wu <us...@gmail.com>
>> wrote:
>> > > > > >
>> > > > > > > I agree that we need to wait for "Make
>> > > > `ColumnMetaData.path_in_schema`
>> > > > > > > optional". I think it has reached consensus and Ed will start
>> a
>> > vote
>> > > > > > > shortly.
>> > > > > > >
>> > > > > > > > Is the ALP change close enough to wait for that too?
>> > > > > > >
>> > > > > > > I'm catching up with its progress. Perhaps active contributors
>> > and
>> > > > > > > reviewers can chime in?
>> > > > > > >
>> > > > > > > On Fri, May 29, 2026 at 10:00 AM Curt Hagenlocher <
>> > > > > curt@hagenlocher.org>
>> > > > > > > wrote:
>> > > > > > > >
>> > > > > > > > Is the ALP change close enough to wait for that too?
>> > > > > > > >
>> > > > > > > > Sent from my iPhone
>> > > > > > > >
>> > > > > > > > > On May 28, 2026, at 3:10 PM, Micah Kornfield <
>> > > > > emkornfield@gmail.com>
>> > > > > > > wrote:
>> > > > > > > > >
>> > > > > > > > > I think if possible landing "Make
>> > > > `ColumnMetaData.path_in_schema`
>> > > > > > > optional"
>> > > > > > > > > would be good to avoid a second release soon after.
>> > > > > > > > >
>> > > > > > > > >> On Thu, May 28, 2026 at 9:00 AM Gang Wu <
>> ustcwg@gmail.com>
>> > > > wrote:
>> > > > > > > > >>
>> > > > > > > > >> Hi all,
>> > > > > > > > >>
>> > > > > > > > >> I would like to start a discussion about a parquet-format
>> > 2.13.0
>> > > > > > > release.
>> > > > > > > > >>
>> > > > > > > > >> It has been about 9 months since 2.12.0 was released on
>> > August
>> > > > 28,
>> > > > > > > 2025.
>> > > > > > > > >>
>> > > > > > > > >> Since then, we have had some meaningful updates,
>> especially:
>> > > > > > > > >>
>> > > > > > > > >> - [PR #514](https://github.com/
>> > apache/parquet-format/pull/514)
>> > > > > > > > >> PARQUET-2249: Introduce IEEE 754 total order & NaN-counts
>> > > > > > > > >> - [PR #565](https://github.com/
>> > apache/parquet-format/pull/565)
>> > > > > > > GH-506:
>> > > > > > > > >> Clarify field ordering for partially shredded object
>> union
>> > > > > > > > >> - [PR #560](https://github.com/
>> > apache/parquet-format/pull/560)
>> > > > > Update
>> > > > > > > > >> wording in Geospatial spec
>> > > > > > > > >> - [PR #562](https://github.com/
>> > apache/parquet-format/pull/562)
>> > > > > > > GH-561:
>> > > > > > > > >> variant schema examples to use `(VARIANT(1))`
>> > > > > > > > >>
>> > > > > > > > >> There are also some open PRs that may be worth waiting
>> for,
>> > > > > > > especially:
>> > > > > > > > >>
>> > > > > > > > >> - [PR #564](https://github.com/
>> > apache/parquet-format/pull/564)
>> > > > > > > GH-563:
>> > > > > > > > >> Make `ColumnMetaData.path_in_schema` optional
>> > > > > > > > >>
>> > > > > > > > >> It looks promising to me, and there is already related
>> > > > > implementation
>> > > > > > > > >> work in arrow-rs, parquet-java, and arrow-cpp. (Thanks
>> Ed!)
>> > > > > > > > >>
>> > > > > > > > >> What do people think?
>> > > > > > > > >>
>> > > > > > > > >> Thanks,
>> > > > > > > > >> Gang
>> > > > > > > > >>
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
>

Re: [DISCUSS] Release parquet-format 2.13.0?

Posted by Gang Wu <us...@gmail.com>.

Vote thread is sent:
https://lists.apache.org/thread/7kjqsz7n8cwqpgfo2h9c5q0csml77d86

On Mon, Jun 8, 2026 at 10:28 PM Micah Kornfield <em...@gmail.com>
wrote:

> I also think it is reasonable to start a release.
>
> Thanks,
> Micah
>
> On Friday, June 5, 2026, Fokko Driesprong <fo...@apache.org> wrote:
>
> > Sounds good, Gang. No objections from my end. Thanks for running this!
> >
> > Kind regards,
> > Fokko
> >
> > On 2026/06/05 03:23:55 Gang Wu wrote:
> > > It seems that the work on making `ColumnMetaData.path_in_schema`
> > optional
> > > still needs more discussion as per [1], so I'm inclined not to wait for
> > it
> > > for the 2.13.0 release.
> > >
> > > Regarding Ismaël's comment [2], I don't think it changes any spec, so
> it
> > > should not block the release and reviewers need more time to read them.
> > >
> > > If there are no objections, I will create a Release Candidate (RC) next
> > > week.
> > >
> > > [1] https://lists.apache.org/thread/gm7btrgvprdbrh8c5nv061f402txo0vt
> > > [2] https://github.com/apache/parquet-format/pull/572
> > >
> > > Best,
> > > Gang
> > >
> > > On Tue, Jun 2, 2026 at 11:38 PM Ismaël Mejía <ie...@gmail.com>
> wrote:
> > >
> > > > I just wanted to mention that, as part of my ongoing AI
> explorations, I
> > > > opened a PR fixing minor issues such as orthography, grammar, and
> some
> > > > snippet errors.
> > > >
> > > > It’s a small PR (~200 lines), so it should be quick to review and,
> > > > hopefully, make it into the next release.
> > > > https://github.com/apache/parquet-format/pull/572
> > > >
> > > > Best,
> > > > Ismaël
> > > >
> > > > On Fri, May 29, 2026 at 11:06 AM Fokko Driesprong <fo...@apache.org>
> > > > wrote:
> > > >
> > > > > +1 for the release
> > > > >
> > > > > I got a small one to bump to the latest version of Thrift to
> supress
> > a
> > > > > CVE: https://github.com/apache/parquet-format/pull/570
> > > > >
> > > > > I don't think we should block releases for format since they are
> > pretty
> > > > > ligthtweight and might unblock downstream consumers.
> > > > >
> > > > > Thanks,
> > > > > Fokko
> > > > >
> > > > > On 2026/05/29 02:40:14 Micah Kornfield wrote:
> > > > > > I need to do another pass on the C++ implementation.  I think I
> saw
> > > > some
> > > > > > other comments on the spec change, which I'm not sure if they are
> > > > > > addressed.
> > > > > >
> > > > > > On Thu, May 28, 2026 at 7:07 PM Gang Wu <us...@gmail.com>
> wrote:
> > > > > >
> > > > > > > I agree that we need to wait for "Make
> > > > `ColumnMetaData.path_in_schema`
> > > > > > > optional". I think it has reached consensus and Ed will start a
> > vote
> > > > > > > shortly.
> > > > > > >
> > > > > > > > Is the ALP change close enough to wait for that too?
> > > > > > >
> > > > > > > I'm catching up with its progress. Perhaps active contributors
> > and
> > > > > > > reviewers can chime in?
> > > > > > >
> > > > > > > On Fri, May 29, 2026 at 10:00 AM Curt Hagenlocher <
> > > > > curt@hagenlocher.org>
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > Is the ALP change close enough to wait for that too?
> > > > > > > >
> > > > > > > > Sent from my iPhone
> > > > > > > >
> > > > > > > > > On May 28, 2026, at 3:10 PM, Micah Kornfield <
> > > > > emkornfield@gmail.com>
> > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > I think if possible landing "Make
> > > > `ColumnMetaData.path_in_schema`
> > > > > > > optional"
> > > > > > > > > would be good to avoid a second release soon after.
> > > > > > > > >
> > > > > > > > >> On Thu, May 28, 2026 at 9:00 AM Gang Wu <ustcwg@gmail.com
> >
> > > > wrote:
> > > > > > > > >>
> > > > > > > > >> Hi all,
> > > > > > > > >>
> > > > > > > > >> I would like to start a discussion about a parquet-format
> > 2.13.0
> > > > > > > release.
> > > > > > > > >>
> > > > > > > > >> It has been about 9 months since 2.12.0 was released on
> > August
> > > > 28,
> > > > > > > 2025.
> > > > > > > > >>
> > > > > > > > >> Since then, we have had some meaningful updates,
> especially:
> > > > > > > > >>
> > > > > > > > >> - [PR #514](https://github.com/
> > apache/parquet-format/pull/514)
> > > > > > > > >> PARQUET-2249: Introduce IEEE 754 total order & NaN-counts
> > > > > > > > >> - [PR #565](https://github.com/
> > apache/parquet-format/pull/565)
> > > > > > > GH-506:
> > > > > > > > >> Clarify field ordering for partially shredded object union
> > > > > > > > >> - [PR #560](https://github.com/
> > apache/parquet-format/pull/560)
> > > > > Update
> > > > > > > > >> wording in Geospatial spec
> > > > > > > > >> - [PR #562](https://github.com/
> > apache/parquet-format/pull/562)
> > > > > > > GH-561:
> > > > > > > > >> variant schema examples to use `(VARIANT(1))`
> > > > > > > > >>
> > > > > > > > >> There are also some open PRs that may be worth waiting
> for,
> > > > > > > especially:
> > > > > > > > >>
> > > > > > > > >> - [PR #564](https://github.com/
> > apache/parquet-format/pull/564)
> > > > > > > GH-563:
> > > > > > > > >> Make `ColumnMetaData.path_in_schema` optional
> > > > > > > > >>
> > > > > > > > >> It looks promising to me, and there is already related
> > > > > implementation
> > > > > > > > >> work in arrow-rs, parquet-java, and arrow-cpp. (Thanks
> Ed!)
> > > > > > > > >>
> > > > > > > > >> What do people think?
> > > > > > > > >>
> > > > > > > > >> Thanks,
> > > > > > > > >> Gang
> > > > > > > > >>
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: [DISCUSS] Release parquet-format 2.13.0?

Posted by Micah Kornfield <em...@gmail.com>.

I also think it is reasonable to start a release.

Thanks,
Micah

On Friday, June 5, 2026, Fokko Driesprong <fo...@apache.org> wrote:

> Sounds good, Gang. No objections from my end. Thanks for running this!
>
> Kind regards,
> Fokko
>
> On 2026/06/05 03:23:55 Gang Wu wrote:
> > It seems that the work on making `ColumnMetaData.path_in_schema`
> optional
> > still needs more discussion as per [1], so I'm inclined not to wait for
> it
> > for the 2.13.0 release.
> >
> > Regarding Ismaël's comment [2], I don't think it changes any spec, so it
> > should not block the release and reviewers need more time to read them.
> >
> > If there are no objections, I will create a Release Candidate (RC) next
> > week.
> >
> > [1] https://lists.apache.org/thread/gm7btrgvprdbrh8c5nv061f402txo0vt
> > [2] https://github.com/apache/parquet-format/pull/572
> >
> > Best,
> > Gang
> >
> > On Tue, Jun 2, 2026 at 11:38 PM Ismaël Mejía <ie...@gmail.com> wrote:
> >
> > > I just wanted to mention that, as part of my ongoing AI explorations, I
> > > opened a PR fixing minor issues such as orthography, grammar, and some
> > > snippet errors.
> > >
> > > It’s a small PR (~200 lines), so it should be quick to review and,
> > > hopefully, make it into the next release.
> > > https://github.com/apache/parquet-format/pull/572
> > >
> > > Best,
> > > Ismaël
> > >
> > > On Fri, May 29, 2026 at 11:06 AM Fokko Driesprong <fo...@apache.org>
> > > wrote:
> > >
> > > > +1 for the release
> > > >
> > > > I got a small one to bump to the latest version of Thrift to supress
> a
> > > > CVE: https://github.com/apache/parquet-format/pull/570
> > > >
> > > > I don't think we should block releases for format since they are
> pretty
> > > > ligthtweight and might unblock downstream consumers.
> > > >
> > > > Thanks,
> > > > Fokko
> > > >
> > > > On 2026/05/29 02:40:14 Micah Kornfield wrote:
> > > > > I need to do another pass on the C++ implementation.  I think I saw
> > > some
> > > > > other comments on the spec change, which I'm not sure if they are
> > > > > addressed.
> > > > >
> > > > > On Thu, May 28, 2026 at 7:07 PM Gang Wu <us...@gmail.com> wrote:
> > > > >
> > > > > > I agree that we need to wait for "Make
> > > `ColumnMetaData.path_in_schema`
> > > > > > optional". I think it has reached consensus and Ed will start a
> vote
> > > > > > shortly.
> > > > > >
> > > > > > > Is the ALP change close enough to wait for that too?
> > > > > >
> > > > > > I'm catching up with its progress. Perhaps active contributors
> and
> > > > > > reviewers can chime in?
> > > > > >
> > > > > > On Fri, May 29, 2026 at 10:00 AM Curt Hagenlocher <
> > > > curt@hagenlocher.org>
> > > > > > wrote:
> > > > > > >
> > > > > > > Is the ALP change close enough to wait for that too?
> > > > > > >
> > > > > > > Sent from my iPhone
> > > > > > >
> > > > > > > > On May 28, 2026, at 3:10 PM, Micah Kornfield <
> > > > emkornfield@gmail.com>
> > > > > > wrote:
> > > > > > > >
> > > > > > > > I think if possible landing "Make
> > > `ColumnMetaData.path_in_schema`
> > > > > > optional"
> > > > > > > > would be good to avoid a second release soon after.
> > > > > > > >
> > > > > > > >> On Thu, May 28, 2026 at 9:00 AM Gang Wu <us...@gmail.com>
> > > wrote:
> > > > > > > >>
> > > > > > > >> Hi all,
> > > > > > > >>
> > > > > > > >> I would like to start a discussion about a parquet-format
> 2.13.0
> > > > > > release.
> > > > > > > >>
> > > > > > > >> It has been about 9 months since 2.12.0 was released on
> August
> > > 28,
> > > > > > 2025.
> > > > > > > >>
> > > > > > > >> Since then, we have had some meaningful updates, especially:
> > > > > > > >>
> > > > > > > >> - [PR #514](https://github.com/
> apache/parquet-format/pull/514)
> > > > > > > >> PARQUET-2249: Introduce IEEE 754 total order & NaN-counts
> > > > > > > >> - [PR #565](https://github.com/
> apache/parquet-format/pull/565)
> > > > > > GH-506:
> > > > > > > >> Clarify field ordering for partially shredded object union
> > > > > > > >> - [PR #560](https://github.com/
> apache/parquet-format/pull/560)
> > > > Update
> > > > > > > >> wording in Geospatial spec
> > > > > > > >> - [PR #562](https://github.com/
> apache/parquet-format/pull/562)
> > > > > > GH-561:
> > > > > > > >> variant schema examples to use `(VARIANT(1))`
> > > > > > > >>
> > > > > > > >> There are also some open PRs that may be worth waiting for,
> > > > > > especially:
> > > > > > > >>
> > > > > > > >> - [PR #564](https://github.com/
> apache/parquet-format/pull/564)
> > > > > > GH-563:
> > > > > > > >> Make `ColumnMetaData.path_in_schema` optional
> > > > > > > >>
> > > > > > > >> It looks promising to me, and there is already related
> > > > implementation
> > > > > > > >> work in arrow-rs, parquet-java, and arrow-cpp. (Thanks Ed!)
> > > > > > > >>
> > > > > > > >> What do people think?
> > > > > > > >>
> > > > > > > >> Thanks,
> > > > > > > >> Gang
> > > > > > > >>
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: [DISCUSS] Release parquet-format 2.13.0?

Posted by Fokko Driesprong <fo...@apache.org>.

Sounds good, Gang. No objections from my end. Thanks for running this!

Kind regards,
Fokko

On 2026/06/05 03:23:55 Gang Wu wrote:
> It seems that the work on making `ColumnMetaData.path_in_schema` optional
> still needs more discussion as per [1], so I'm inclined not to wait for it
> for the 2.13.0 release.
> 
> Regarding Ismaël's comment [2], I don't think it changes any spec, so it
> should not block the release and reviewers need more time to read them.
> 
> If there are no objections, I will create a Release Candidate (RC) next
> week.
> 
> [1] https://lists.apache.org/thread/gm7btrgvprdbrh8c5nv061f402txo0vt
> [2] https://github.com/apache/parquet-format/pull/572
> 
> Best,
> Gang
> 
> On Tue, Jun 2, 2026 at 11:38 PM Ismaël Mejía <ie...@gmail.com> wrote:
> 
> > I just wanted to mention that, as part of my ongoing AI explorations, I
> > opened a PR fixing minor issues such as orthography, grammar, and some
> > snippet errors.
> >
> > It’s a small PR (~200 lines), so it should be quick to review and,
> > hopefully, make it into the next release.
> > https://github.com/apache/parquet-format/pull/572
> >
> > Best,
> > Ismaël
> >
> > On Fri, May 29, 2026 at 11:06 AM Fokko Driesprong <fo...@apache.org>
> > wrote:
> >
> > > +1 for the release
> > >
> > > I got a small one to bump to the latest version of Thrift to supress a
> > > CVE: https://github.com/apache/parquet-format/pull/570
> > >
> > > I don't think we should block releases for format since they are pretty
> > > ligthtweight and might unblock downstream consumers.
> > >
> > > Thanks,
> > > Fokko
> > >
> > > On 2026/05/29 02:40:14 Micah Kornfield wrote:
> > > > I need to do another pass on the C++ implementation.  I think I saw
> > some
> > > > other comments on the spec change, which I'm not sure if they are
> > > > addressed.
> > > >
> > > > On Thu, May 28, 2026 at 7:07 PM Gang Wu <us...@gmail.com> wrote:
> > > >
> > > > > I agree that we need to wait for "Make
> > `ColumnMetaData.path_in_schema`
> > > > > optional". I think it has reached consensus and Ed will start a vote
> > > > > shortly.
> > > > >
> > > > > > Is the ALP change close enough to wait for that too?
> > > > >
> > > > > I'm catching up with its progress. Perhaps active contributors and
> > > > > reviewers can chime in?
> > > > >
> > > > > On Fri, May 29, 2026 at 10:00 AM Curt Hagenlocher <
> > > curt@hagenlocher.org>
> > > > > wrote:
> > > > > >
> > > > > > Is the ALP change close enough to wait for that too?
> > > > > >
> > > > > > Sent from my iPhone
> > > > > >
> > > > > > > On May 28, 2026, at 3:10 PM, Micah Kornfield <
> > > emkornfield@gmail.com>
> > > > > wrote:
> > > > > > >
> > > > > > > I think if possible landing "Make
> > `ColumnMetaData.path_in_schema`
> > > > > optional"
> > > > > > > would be good to avoid a second release soon after.
> > > > > > >
> > > > > > >> On Thu, May 28, 2026 at 9:00 AM Gang Wu <us...@gmail.com>
> > wrote:
> > > > > > >>
> > > > > > >> Hi all,
> > > > > > >>
> > > > > > >> I would like to start a discussion about a parquet-format 2.13.0
> > > > > release.
> > > > > > >>
> > > > > > >> It has been about 9 months since 2.12.0 was released on August
> > 28,
> > > > > 2025.
> > > > > > >>
> > > > > > >> Since then, we have had some meaningful updates, especially:
> > > > > > >>
> > > > > > >> - [PR #514](https://github.com/apache/parquet-format/pull/514)
> > > > > > >> PARQUET-2249: Introduce IEEE 754 total order & NaN-counts
> > > > > > >> - [PR #565](https://github.com/apache/parquet-format/pull/565)
> > > > > GH-506:
> > > > > > >> Clarify field ordering for partially shredded object union
> > > > > > >> - [PR #560](https://github.com/apache/parquet-format/pull/560)
> > > Update
> > > > > > >> wording in Geospatial spec
> > > > > > >> - [PR #562](https://github.com/apache/parquet-format/pull/562)
> > > > > GH-561:
> > > > > > >> variant schema examples to use `(VARIANT(1))`
> > > > > > >>
> > > > > > >> There are also some open PRs that may be worth waiting for,
> > > > > especially:
> > > > > > >>
> > > > > > >> - [PR #564](https://github.com/apache/parquet-format/pull/564)
> > > > > GH-563:
> > > > > > >> Make `ColumnMetaData.path_in_schema` optional
> > > > > > >>
> > > > > > >> It looks promising to me, and there is already related
> > > implementation
> > > > > > >> work in arrow-rs, parquet-java, and arrow-cpp. (Thanks Ed!)
> > > > > > >>
> > > > > > >> What do people think?
> > > > > > >>
> > > > > > >> Thanks,
> > > > > > >> Gang
> > > > > > >>
> > > > >
> > > >
> > >
> >
>

Re: [DISCUSS] Release parquet-format 2.13.0?

Posted by Gang Wu <us...@gmail.com>.

It seems that the work on making `ColumnMetaData.path_in_schema` optional
still needs more discussion as per [1], so I'm inclined not to wait for it
for the 2.13.0 release.

Regarding Ismaël's comment [2], I don't think it changes any spec, so it
should not block the release and reviewers need more time to read them.

If there are no objections, I will create a Release Candidate (RC) next
week.

[1] https://lists.apache.org/thread/gm7btrgvprdbrh8c5nv061f402txo0vt
[2] https://github.com/apache/parquet-format/pull/572

Best,
Gang

On Tue, Jun 2, 2026 at 11:38 PM Ismaël Mejía <ie...@gmail.com> wrote:

> I just wanted to mention that, as part of my ongoing AI explorations, I
> opened a PR fixing minor issues such as orthography, grammar, and some
> snippet errors.
>
> It’s a small PR (~200 lines), so it should be quick to review and,
> hopefully, make it into the next release.
> https://github.com/apache/parquet-format/pull/572
>
> Best,
> Ismaël
>
> On Fri, May 29, 2026 at 11:06 AM Fokko Driesprong <fo...@apache.org>
> wrote:
>
> > +1 for the release
> >
> > I got a small one to bump to the latest version of Thrift to supress a
> > CVE: https://github.com/apache/parquet-format/pull/570
> >
> > I don't think we should block releases for format since they are pretty
> > ligthtweight and might unblock downstream consumers.
> >
> > Thanks,
> > Fokko
> >
> > On 2026/05/29 02:40:14 Micah Kornfield wrote:
> > > I need to do another pass on the C++ implementation.  I think I saw
> some
> > > other comments on the spec change, which I'm not sure if they are
> > > addressed.
> > >
> > > On Thu, May 28, 2026 at 7:07 PM Gang Wu <us...@gmail.com> wrote:
> > >
> > > > I agree that we need to wait for "Make
> `ColumnMetaData.path_in_schema`
> > > > optional". I think it has reached consensus and Ed will start a vote
> > > > shortly.
> > > >
> > > > > Is the ALP change close enough to wait for that too?
> > > >
> > > > I'm catching up with its progress. Perhaps active contributors and
> > > > reviewers can chime in?
> > > >
> > > > On Fri, May 29, 2026 at 10:00 AM Curt Hagenlocher <
> > curt@hagenlocher.org>
> > > > wrote:
> > > > >
> > > > > Is the ALP change close enough to wait for that too?
> > > > >
> > > > > Sent from my iPhone
> > > > >
> > > > > > On May 28, 2026, at 3:10 PM, Micah Kornfield <
> > emkornfield@gmail.com>
> > > > wrote:
> > > > > >
> > > > > > I think if possible landing "Make
> `ColumnMetaData.path_in_schema`
> > > > optional"
> > > > > > would be good to avoid a second release soon after.
> > > > > >
> > > > > >> On Thu, May 28, 2026 at 9:00 AM Gang Wu <us...@gmail.com>
> wrote:
> > > > > >>
> > > > > >> Hi all,
> > > > > >>
> > > > > >> I would like to start a discussion about a parquet-format 2.13.0
> > > > release.
> > > > > >>
> > > > > >> It has been about 9 months since 2.12.0 was released on August
> 28,
> > > > 2025.
> > > > > >>
> > > > > >> Since then, we have had some meaningful updates, especially:
> > > > > >>
> > > > > >> - [PR #514](https://github.com/apache/parquet-format/pull/514)
> > > > > >> PARQUET-2249: Introduce IEEE 754 total order & NaN-counts
> > > > > >> - [PR #565](https://github.com/apache/parquet-format/pull/565)
> > > > GH-506:
> > > > > >> Clarify field ordering for partially shredded object union
> > > > > >> - [PR #560](https://github.com/apache/parquet-format/pull/560)
> > Update
> > > > > >> wording in Geospatial spec
> > > > > >> - [PR #562](https://github.com/apache/parquet-format/pull/562)
> > > > GH-561:
> > > > > >> variant schema examples to use `(VARIANT(1))`
> > > > > >>
> > > > > >> There are also some open PRs that may be worth waiting for,
> > > > especially:
> > > > > >>
> > > > > >> - [PR #564](https://github.com/apache/parquet-format/pull/564)
> > > > GH-563:
> > > > > >> Make `ColumnMetaData.path_in_schema` optional
> > > > > >>
> > > > > >> It looks promising to me, and there is already related
> > implementation
> > > > > >> work in arrow-rs, parquet-java, and arrow-cpp. (Thanks Ed!)
> > > > > >>
> > > > > >> What do people think?
> > > > > >>
> > > > > >> Thanks,
> > > > > >> Gang
> > > > > >>
> > > >
> > >
> >
>

Re: [DISCUSS] Release parquet-format 2.13.0?

Posted by Ismaël Mejía <ie...@gmail.com>.

I just wanted to mention that, as part of my ongoing AI explorations, I
opened a PR fixing minor issues such as orthography, grammar, and some
snippet errors.

It’s a small PR (~200 lines), so it should be quick to review and,
hopefully, make it into the next release.
https://github.com/apache/parquet-format/pull/572

Best,
Ismaël

On Fri, May 29, 2026 at 11:06 AM Fokko Driesprong <fo...@apache.org> wrote:

> +1 for the release
>
> I got a small one to bump to the latest version of Thrift to supress a
> CVE: https://github.com/apache/parquet-format/pull/570
>
> I don't think we should block releases for format since they are pretty
> ligthtweight and might unblock downstream consumers.
>
> Thanks,
> Fokko
>
> On 2026/05/29 02:40:14 Micah Kornfield wrote:
> > I need to do another pass on the C++ implementation.  I think I saw some
> > other comments on the spec change, which I'm not sure if they are
> > addressed.
> >
> > On Thu, May 28, 2026 at 7:07 PM Gang Wu <us...@gmail.com> wrote:
> >
> > > I agree that we need to wait for "Make `ColumnMetaData.path_in_schema`
> > > optional". I think it has reached consensus and Ed will start a vote
> > > shortly.
> > >
> > > > Is the ALP change close enough to wait for that too?
> > >
> > > I'm catching up with its progress. Perhaps active contributors and
> > > reviewers can chime in?
> > >
> > > On Fri, May 29, 2026 at 10:00 AM Curt Hagenlocher <
> curt@hagenlocher.org>
> > > wrote:
> > > >
> > > > Is the ALP change close enough to wait for that too?
> > > >
> > > > Sent from my iPhone
> > > >
> > > > > On May 28, 2026, at 3:10 PM, Micah Kornfield <
> emkornfield@gmail.com>
> > > wrote:
> > > > >
> > > > > I think if possible landing "Make `ColumnMetaData.path_in_schema`
> > > optional"
> > > > > would be good to avoid a second release soon after.
> > > > >
> > > > >> On Thu, May 28, 2026 at 9:00 AM Gang Wu <us...@gmail.com> wrote:
> > > > >>
> > > > >> Hi all,
> > > > >>
> > > > >> I would like to start a discussion about a parquet-format 2.13.0
> > > release.
> > > > >>
> > > > >> It has been about 9 months since 2.12.0 was released on August 28,
> > > 2025.
> > > > >>
> > > > >> Since then, we have had some meaningful updates, especially:
> > > > >>
> > > > >> - [PR #514](https://github.com/apache/parquet-format/pull/514)
> > > > >> PARQUET-2249: Introduce IEEE 754 total order & NaN-counts
> > > > >> - [PR #565](https://github.com/apache/parquet-format/pull/565)
> > > GH-506:
> > > > >> Clarify field ordering for partially shredded object union
> > > > >> - [PR #560](https://github.com/apache/parquet-format/pull/560)
> Update
> > > > >> wording in Geospatial spec
> > > > >> - [PR #562](https://github.com/apache/parquet-format/pull/562)
> > > GH-561:
> > > > >> variant schema examples to use `(VARIANT(1))`
> > > > >>
> > > > >> There are also some open PRs that may be worth waiting for,
> > > especially:
> > > > >>
> > > > >> - [PR #564](https://github.com/apache/parquet-format/pull/564)
> > > GH-563:
> > > > >> Make `ColumnMetaData.path_in_schema` optional
> > > > >>
> > > > >> It looks promising to me, and there is already related
> implementation
> > > > >> work in arrow-rs, parquet-java, and arrow-cpp. (Thanks Ed!)
> > > > >>
> > > > >> What do people think?
> > > > >>
> > > > >> Thanks,
> > > > >> Gang
> > > > >>
> > >
> >
>

Re: [DISCUSS] Release parquet-format 2.13.0?

Posted by Fokko Driesprong <fo...@apache.org>.

+1 for the release

I got a small one to bump to the latest version of Thrift to supress a CVE: https://github.com/apache/parquet-format/pull/570

I don't think we should block releases for format since they are pretty ligthtweight and might unblock downstream consumers.

Thanks,
Fokko

On 2026/05/29 02:40:14 Micah Kornfield wrote:
> I need to do another pass on the C++ implementation.  I think I saw some
> other comments on the spec change, which I'm not sure if they are
> addressed.
> 
> On Thu, May 28, 2026 at 7:07 PM Gang Wu <us...@gmail.com> wrote:
> 
> > I agree that we need to wait for "Make `ColumnMetaData.path_in_schema`
> > optional". I think it has reached consensus and Ed will start a vote
> > shortly.
> >
> > > Is the ALP change close enough to wait for that too?
> >
> > I'm catching up with its progress. Perhaps active contributors and
> > reviewers can chime in?
> >
> > On Fri, May 29, 2026 at 10:00 AM Curt Hagenlocher <cu...@hagenlocher.org>
> > wrote:
> > >
> > > Is the ALP change close enough to wait for that too?
> > >
> > > Sent from my iPhone
> > >
> > > > On May 28, 2026, at 3:10 PM, Micah Kornfield <em...@gmail.com>
> > wrote:
> > > >
> > > > I think if possible landing "Make `ColumnMetaData.path_in_schema`
> > optional"
> > > > would be good to avoid a second release soon after.
> > > >
> > > >> On Thu, May 28, 2026 at 9:00 AM Gang Wu <us...@gmail.com> wrote:
> > > >>
> > > >> Hi all,
> > > >>
> > > >> I would like to start a discussion about a parquet-format 2.13.0
> > release.
> > > >>
> > > >> It has been about 9 months since 2.12.0 was released on August 28,
> > 2025.
> > > >>
> > > >> Since then, we have had some meaningful updates, especially:
> > > >>
> > > >> - [PR #514](https://github.com/apache/parquet-format/pull/514)
> > > >> PARQUET-2249: Introduce IEEE 754 total order & NaN-counts
> > > >> - [PR #565](https://github.com/apache/parquet-format/pull/565)
> > GH-506:
> > > >> Clarify field ordering for partially shredded object union
> > > >> - [PR #560](https://github.com/apache/parquet-format/pull/560) Update
> > > >> wording in Geospatial spec
> > > >> - [PR #562](https://github.com/apache/parquet-format/pull/562)
> > GH-561:
> > > >> variant schema examples to use `(VARIANT(1))`
> > > >>
> > > >> There are also some open PRs that may be worth waiting for,
> > especially:
> > > >>
> > > >> - [PR #564](https://github.com/apache/parquet-format/pull/564)
> > GH-563:
> > > >> Make `ColumnMetaData.path_in_schema` optional
> > > >>
> > > >> It looks promising to me, and there is already related implementation
> > > >> work in arrow-rs, parquet-java, and arrow-cpp. (Thanks Ed!)
> > > >>
> > > >> What do people think?
> > > >>
> > > >> Thanks,
> > > >> Gang
> > > >>
> >
>

Re: [DISCUSS] Release parquet-format 2.13.0?

Posted by Micah Kornfield <em...@gmail.com>.

I need to do another pass on the C++ implementation.  I think I saw some
other comments on the spec change, which I'm not sure if they are
addressed.

On Thu, May 28, 2026 at 7:07 PM Gang Wu <us...@gmail.com> wrote:

> I agree that we need to wait for "Make `ColumnMetaData.path_in_schema`
> optional". I think it has reached consensus and Ed will start a vote
> shortly.
>
> > Is the ALP change close enough to wait for that too?
>
> I'm catching up with its progress. Perhaps active contributors and
> reviewers can chime in?
>
> On Fri, May 29, 2026 at 10:00 AM Curt Hagenlocher <cu...@hagenlocher.org>
> wrote:
> >
> > Is the ALP change close enough to wait for that too?
> >
> > Sent from my iPhone
> >
> > > On May 28, 2026, at 3:10 PM, Micah Kornfield <em...@gmail.com>
> wrote:
> > >
> > > I think if possible landing "Make `ColumnMetaData.path_in_schema`
> optional"
> > > would be good to avoid a second release soon after.
> > >
> > >> On Thu, May 28, 2026 at 9:00 AM Gang Wu <us...@gmail.com> wrote:
> > >>
> > >> Hi all,
> > >>
> > >> I would like to start a discussion about a parquet-format 2.13.0
> release.
> > >>
> > >> It has been about 9 months since 2.12.0 was released on August 28,
> 2025.
> > >>
> > >> Since then, we have had some meaningful updates, especially:
> > >>
> > >> - [PR #514](https://github.com/apache/parquet-format/pull/514)
> > >> PARQUET-2249: Introduce IEEE 754 total order & NaN-counts
> > >> - [PR #565](https://github.com/apache/parquet-format/pull/565)
> GH-506:
> > >> Clarify field ordering for partially shredded object union
> > >> - [PR #560](https://github.com/apache/parquet-format/pull/560) Update
> > >> wording in Geospatial spec
> > >> - [PR #562](https://github.com/apache/parquet-format/pull/562)
> GH-561:
> > >> variant schema examples to use `(VARIANT(1))`
> > >>
> > >> There are also some open PRs that may be worth waiting for,
> especially:
> > >>
> > >> - [PR #564](https://github.com/apache/parquet-format/pull/564)
> GH-563:
> > >> Make `ColumnMetaData.path_in_schema` optional
> > >>
> > >> It looks promising to me, and there is already related implementation
> > >> work in arrow-rs, parquet-java, and arrow-cpp. (Thanks Ed!)
> > >>
> > >> What do people think?
> > >>
> > >> Thanks,
> > >> Gang
> > >>
>

Re: [DISCUSS] Release parquet-format 2.13.0?

Posted by Gang Wu <us...@gmail.com>.

I agree that we need to wait for "Make `ColumnMetaData.path_in_schema`
optional". I think it has reached consensus and Ed will start a vote
shortly.

> Is the ALP change close enough to wait for that too?

I'm catching up with its progress. Perhaps active contributors and
reviewers can chime in?

On Fri, May 29, 2026 at 10:00 AM Curt Hagenlocher <cu...@hagenlocher.org> wrote:
>
> Is the ALP change close enough to wait for that too?
>
> Sent from my iPhone
>
> > On May 28, 2026, at 3:10 PM, Micah Kornfield <em...@gmail.com> wrote:
> >
> > I think if possible landing "Make `ColumnMetaData.path_in_schema` optional"
> > would be good to avoid a second release soon after.
> >
> >> On Thu, May 28, 2026 at 9:00 AM Gang Wu <us...@gmail.com> wrote:
> >>
> >> Hi all,
> >>
> >> I would like to start a discussion about a parquet-format 2.13.0 release.
> >>
> >> It has been about 9 months since 2.12.0 was released on August 28, 2025.
> >>
> >> Since then, we have had some meaningful updates, especially:
> >>
> >> - [PR #514](https://github.com/apache/parquet-format/pull/514)
> >> PARQUET-2249: Introduce IEEE 754 total order & NaN-counts
> >> - [PR #565](https://github.com/apache/parquet-format/pull/565) GH-506:
> >> Clarify field ordering for partially shredded object union
> >> - [PR #560](https://github.com/apache/parquet-format/pull/560) Update
> >> wording in Geospatial spec
> >> - [PR #562](https://github.com/apache/parquet-format/pull/562) GH-561:
> >> variant schema examples to use `(VARIANT(1))`
> >>
> >> There are also some open PRs that may be worth waiting for, especially:
> >>
> >> - [PR #564](https://github.com/apache/parquet-format/pull/564) GH-563:
> >> Make `ColumnMetaData.path_in_schema` optional
> >>
> >> It looks promising to me, and there is already related implementation
> >> work in arrow-rs, parquet-java, and arrow-cpp. (Thanks Ed!)
> >>
> >> What do people think?
> >>
> >> Thanks,
> >> Gang
> >>

Re: [DISCUSS] Release parquet-format 2.13.0?

Posted by Curt Hagenlocher <cu...@hagenlocher.org>.

Is the ALP change close enough to wait for that too?

Sent from my iPhone

> On May 28, 2026, at 3:10 PM, Micah Kornfield <em...@gmail.com> wrote:
> 
> I think if possible landing "Make `ColumnMetaData.path_in_schema` optional"
> would be good to avoid a second release soon after.
> 
>> On Thu, May 28, 2026 at 9:00 AM Gang Wu <us...@gmail.com> wrote:
>> 
>> Hi all,
>> 
>> I would like to start a discussion about a parquet-format 2.13.0 release.
>> 
>> It has been about 9 months since 2.12.0 was released on August 28, 2025.
>> 
>> Since then, we have had some meaningful updates, especially:
>> 
>> - [PR #514](https://github.com/apache/parquet-format/pull/514)
>> PARQUET-2249: Introduce IEEE 754 total order & NaN-counts
>> - [PR #565](https://github.com/apache/parquet-format/pull/565) GH-506:
>> Clarify field ordering for partially shredded object union
>> - [PR #560](https://github.com/apache/parquet-format/pull/560) Update
>> wording in Geospatial spec
>> - [PR #562](https://github.com/apache/parquet-format/pull/562) GH-561:
>> variant schema examples to use `(VARIANT(1))`
>> 
>> There are also some open PRs that may be worth waiting for, especially:
>> 
>> - [PR #564](https://github.com/apache/parquet-format/pull/564) GH-563:
>> Make `ColumnMetaData.path_in_schema` optional
>> 
>> It looks promising to me, and there is already related implementation
>> work in arrow-rs, parquet-java, and arrow-cpp. (Thanks Ed!)
>> 
>> What do people think?
>> 
>> Thanks,
>> Gang
>>

Re: [DISCUSS] Release parquet-format 2.13.0?

Posted by Micah Kornfield <em...@gmail.com>.

I think if possible landing "Make `ColumnMetaData.path_in_schema` optional"
would be good to avoid a second release soon after.

On Thu, May 28, 2026 at 9:00 AM Gang Wu <us...@gmail.com> wrote:

> Hi all,
>
> I would like to start a discussion about a parquet-format 2.13.0 release.
>
> It has been about 9 months since 2.12.0 was released on August 28, 2025.
>
> Since then, we have had some meaningful updates, especially:
>
> - [PR #514](https://github.com/apache/parquet-format/pull/514)
> PARQUET-2249: Introduce IEEE 754 total order & NaN-counts
> - [PR #565](https://github.com/apache/parquet-format/pull/565) GH-506:
> Clarify field ordering for partially shredded object union
> - [PR #560](https://github.com/apache/parquet-format/pull/560) Update
> wording in Geospatial spec
> - [PR #562](https://github.com/apache/parquet-format/pull/562) GH-561:
> variant schema examples to use `(VARIANT(1))`
>
> There are also some open PRs that may be worth waiting for, especially:
>
> - [PR #564](https://github.com/apache/parquet-format/pull/564) GH-563:
> Make `ColumnMetaData.path_in_schema` optional
>
> It looks promising to me, and there is already related implementation
> work in arrow-rs, parquet-java, and arrow-cpp. (Thanks Ed!)
>
> What do people think?
>
> Thanks,
> Gang
>