joe-ucp commented on code in PR #8860:
URL: https://github.com/apache/arrow-rs/pull/8860#discussion_r2535699733


##########
CHANGELOG.md:
##########
@@ -29,6 +29,7 @@
 - feat: Improve DataType display for `RunEndEncoded` 
[\#8596](https://github.com/apache/arrow-rs/pull/8596) 
[[arrow](https://github.com/apache/arrow-rs/labels/arrow)] 
([Weijun-H](https://github.com/Weijun-H))
 - Add `ArrowError::AvroError`, remaining types and roundtrip tests to 
`arrow-avro`,  [\#8595](https://github.com/apache/arrow-rs/pull/8595) 
[[arrow](https://github.com/apache/arrow-rs/labels/arrow)] 
([jecsand838](https://github.com/jecsand838))
 - \[thrift-remodel\] Refactor Thrift encryption and store encodings as bitmask 
[\#8587](https://github.com/apache/arrow-rs/pull/8587) 
[[parquet](https://github.com/apache/arrow-rs/labels/parquet)] 
([etseidl](https://github.com/etseidl))
+- Change default page encoding stats decoding mode from `Full` to `Mask` in 
`ParquetMetaDataOptions` [\#8859](https://github.com/apache/arrow-rs/pull/8859) 
[[parquet](https://github.com/apache/arrow-rs/labels/parquet)] 
([user](https://github.com/user))

Review Comment:
   @alamb Thanks for calling this out, and for the link to the AI-assisted 
contribution guidelines.
   
   You’re right: I used an LLM/Copilot-style workflow to help draft this 
change. I did run `cargo fmt`, `cargo clippy`, and `cargo test -p parquet`, but 
I’m still pretty new to Git/GitHub flow and self-taught, so I missed that I 
shouldn’t touch the changelog for already released versions and that I was 
overlaping with the work in #8797.
   
   For this PR I’m happy to let it be closed in favor of #8797.
   
   I’ll make sure future contributions are better self-reviewed before I open a 
PR and that I follow the AI guidelines you linked. Thanks again for the 
feedback (and the patience)!



-- 
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