westonpace commented on issue #14792: URL: https://github.com/apache/arrow/issues/14792#issuecomment-1349949748
> Right, I guess there wouldn't be an alternative in that case. I suppose that also explains why BlockParsingOperator doesn't concern itself with thread-safety either while BlockDecodingOperator does (after the initial block) - since it's the "outermost" mapped generator before readahead gets applied. Even the decoding operator doesn't (I think) need to concern itself with thread-safety. My original intention was that both decoding and parsing would be thread safe and run in parallel. However, I never finished that. -- 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]
