ethe commented on issue #6327: URL: https://github.com/apache/arrow-rs/issues/6327#issuecomment-2317550421
> Additionally, it doesn't make sense given our context could involve S3, Azure Blob, or GCS storage services. It does make sense in local filesystems, which allows to implements `AsyncFileWriter`. > First of all, allowing users to manipulate the writer after AsyncArrowWriter has written the header and data could be error-prone However, `&mut tokio::io::AsyncWriter` is a valid `AsyncFileWriter` in the current, if you think parquet should not allow `&mut AsyncFileWriter` be an `AsyncFileWriter`, then I think `&mut tokio::io::AsyncWriter` should be fixed. What ever happends, the behavior of `tokio::io::AsyncWriter` and non-AsyncWriter should be aligned. -- 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]
