masumi-ryugo commented on PR #9883: URL: https://github.com/apache/arrow-rs/pull/9883#issuecomment-4378766398
Closing this — agreed it's premature in this shape. The more fundamental issue I should have called out in the PR description: `bytes_remaining` on `ThriftReadInputProtocol` (the `Read`-backed variant) defaults to `usize::MAX`, so the proposed trait method gives zero defense against streaming/async readers — only the sliced case. That's not a complete enough mitigation to justify adding a new public trait surface. Will revisit the broader allocation-bounding question under #9874 if a shape that covers both the sliced and `Read` paths becomes clear. Thanks for the read. -- 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]
