Skip to content

[59_maintenance] Backport parquet-testing revision update for ALP tests - #10871

Merged
alamb merged 1 commit into
apache:59_maintenancefrom
alamb:alamb/backport_10786
Aug 26, 2026
Merged

[59_maintenance] Backport parquet-testing revision update for ALP tests#10871
alamb merged 1 commit into
apache:59_maintenancefrom
alamb:alamb/backport_10786

Conversation

@alamb

@alamb alamb commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

Which issue does this PR close?

N/A

Rationale for this change

Backport #10786 to the 59_maintenance branch -- so I don't hit an error validating the release

What changes are included in this PR?

Cherry-pick of 0e58155 (#10786):

  1. Update the parquet-testing submodule to 09f3cdbd
  2. Add the new variants entry to the known files list in the bad_data test

The submodule pointer had a trivial conflict with the revision on 59_maintenance (ffdcbb5e); it was resolved by taking the newer revision from #10786, of which ffdcbb5e is an ancestor.

Are these changes tested?

By CI

Are there any user-facing changes?

No

<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases.
You can link an issue to this PR using the GitHub syntax.
-->

- Closes #NNN.

<!--
Why are you proposing this change? If this is already explained clearly
in the issue then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand
your changes and offer better suggestions for fixes.
-->

<!--
There is no need to duplicate the description in the issue here but it
is sometimes worth providing a summary of the individual changes in this
PR.
-->

<!--
We typically require tests for all PRs in order to:
1. Prevent the code from being accidentally broken by subsequent changes
2. Serve as another way to document the expected behavior of the code

If tests are not included in your PR, please explain why (for example,
are they covered by existing tests)?

If this PR claims a performance improvement, please include evidence
such as benchmark results.
-->

<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.

If there are any breaking changes to public APIs, please call them out.
-->

(cherry picked from commit 0e58155)
@github-actions github-actions Bot added the parquet Changes to the parquet crate label Aug 26, 2026
@alamb
alamb merged commit f90e061 into apache:59_maintenance Aug 26, 2026
17 of 18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

parquet Changes to the parquet crate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants