Hanayoshi-8744 opened a new pull request, #53932:
URL: https://github.com/apache/arrow/pull/53932

   ### Rationale for this change
   
   Thrift 0.25.0 was released shortly after #51559 (bump to 0.24.0) was opened, 
so bump the bundled version again to keep up with the latest release for 27.0.0.
   
   ### What changes are included in this PR?
   
   - Bump the bundled Apache Thrift from 0.24.0 to 0.25.0 in 
`cpp/thirdparty/versions.txt`. The SHA256 matches the one published at 
downloads.apache.org.
   
   ### Are these changes tested?
   
   - Compared the 0.24.0 and 0.25.0 sources of the Thrift headers Arrow uses 
(`TCompactProtocol`, `TMemoryBuffer` in `TBufferTransports.h`, 
`TApplicationException`). The differences are const-correctness, explicit 
casts, and opt-in additions mainly for `TFramedTransport`; I found no change in 
the default behavior of `TMemoryBuffer`.
   - Built Arrow C++ locally on macOS (arm64, AppleClang) with 
`-DARROW_PARQUET=ON -DARROW_BUILD_TESTS=ON -DThrift_SOURCE=BUNDLED` on top of 
the current `main`, and ran `parquet-internals-test`, 
`parquet-file-deserialize-test`, `parquet-schema-test`, `parquet-reader-test`, 
`parquet-writer-test`, `parquet-arrow-reader-writer-test`, 
`parquet-arrow-metadata-test`, `parquet-arrow-index-test`, and 
`parquet-arrow-internals-test`. All passed (some tests were skipped, e.g. those 
requiring Snappy, which was not enabled in my build).
   - Not tested locally: Linux, Windows, and the R package builds; these rely 
on CI.
   
   ### Are there any user-facing changes?
   
   No.
   
   * GitHub Issue: #53931
   
   ---
   
   Disclosure: this change was prepared with the assistance of an AI coding 
tool (Claude Code). I reviewed the diff and ran the tests locally before 
opening this PR.
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to