Release arrow-rs / parquet patch version 54.2.1 (Feb 2025) (HOTFIX)

[Xuanwo]

Is your feature request related to a problem or challenge? Please describe what you are trying to do.

Our release schedule is here https://github.com/apache/arrow-rs?tab=readme-ov-file#release-versioning-and-schedule

This patch release is to backport the hotfix for chrono.

Wishlist Items

• fix: Use chrono >= 0.4.34, < 0.4.40 to avoid breaking #7210

Describe the solution you'd like

Create a release

• Release notes and bump version: [54.2.0_maintenance] Bump arrow version to 54.2.1 #7207
• Release Candidate + Vote thread: https://lists.apache.org/thread/m1pm83ylkty85qn7q3v1pcfx8xsbmpmc
• Release to crates.io / approval: https://lists.apache.org/thread/yjcjkv79d3wkpoj5d41y9q8ozvld3kxl

Describe alternatives you've considered

Additional context

[alamb]

I will be the RM / create / publish this release

[alamb]

Per @Xuanwo 's request on #7207 (comment) , given this is causing people pain downstream, we would like to do an emergency hotfix. I will post to the arrow dev list as well

I request that this release be made under emergency circumstances, allowing it to be released as soon as possible after gathering three +1 binding votes, without waiting for three days.

[alamb]

Posted a note to dev list: https://lists.apache.org/thread/nxj63xzfov2rbcfry8f1d11zqg970tby

[alamb]

I made a PR to DataFusion to test this fix and it seems to have worked well:

• TESTING (NOT FOR MERGE) Test arrow/parquet 54.2.1 datafusion#14915

[alamb]

Voting thread is started: https://lists.apache.org/thread/m1pm83ylkty85qn7q3v1pcfx8xsbmpmc

[alamb]

The release was approved and released to crates.io:
Mailing list: https://lists.apache.org/thread/yjcjkv79d3wkpoj5d41y9q8ozvld3kxl

[Xuanwo]

Thank you so much, @alamb and @tustvold, for handling this release! ASF releases can be completed in just a few hours!

[alamb]

Thank you so much, @alamb and @tustvold, for handling this release! ASF releases can be completed in just a few hours!

Indeed -- thank you @Xuanwo for doing the work to identify the issue and backport the changes, etc ❤

[Xuanwo]

I shared a post according to this release: https://xuanwo.io/links/2025/02/release-arrow-rust-54-2-1-in-6-hours/

[alamb]

Here is my summary of what happened here for anyone who is curious:

1. an arrow-rs dependency ('chrono', a Rust date/time library) released a version 0.4.40 which added a new function quarter, to an existing type. Such an addition is normally "non breaking"
2. However, in this case arrow-rs already provided a quarter function with the same name (using a so-called Rust extension Trait).
3. Thus, when downstream projects upgraded to the (supposedly) compatible new version of chrono, there was now a name conflict causing a compiler error

The fix for downstream users would be to not upgrade chrono (or "pin it to a specific version") which requires changes to their build systems. Here is an example of doing so at Tiledb

Some downstream projects automatically pick up new compatible versions of crates, and thus simply doing cargo update would then not compile.

Our hotfix, included one change from @Xuanwo and @tustvold in #7210. This change updates the Cargo.toml metadata file for arrow-rs (no actual Rust code changes) to explicitly say arrow-rs is not compatible with the new version of chrono, and thus preventing all downstream projects from having to individually do so.

[alamb]

label_issue.py automatically added labels {'arrow'} from #7198