mapleFU opened a new issue, #34722: URL: https://github.com/apache/arrow/issues/34722
### Describe the enhancement requested In C++ Parquet, `SerializedPageReader` holds a `decryption_buffer_` and `decompression_buffer_`, and when `NextPage` called, it will reuse that buffer. So, `Page`'s buffer data is bounded on `SerializedPageReader::NextPage`, when NextPage is called, it's data might be reset. I have two problems here: 1. If it's by design, why don't we cache raw data in SerializePageReader? 2. Should we note these in comments? ### Component(s) C++, Parquet -- 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]
