You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@arrow.apache.org by "tustvold (via GitHub)" <gi...@apache.org> on 2023/04/10 16:14:54 UTC

[GitHub] [arrow-rs] tustvold commented on a diff in pull request #4046: Document Async decoder usage (#4043) (#78)

tustvold commented on code in PR #4046:
URL: https://github.com/apache/arrow-rs/pull/4046#discussion_r1161861084


##########
arrow-csv/src/reader/mod.rs:
##########
@@ -39,6 +41,84 @@
 //! let mut csv = Reader::new(file, Arc::new(schema), false, None, 1024, None, None, None);
 //! let batch = csv.next().unwrap().unwrap();
 //! ```
+//!
+//! # Async Usage
+//!
+//! The lower-level [`Decoder`] can be integrated with various forms of async data streams.

Review Comment:
   The "various forms" here is key, the major problem with the async ecosystem is there is no one-size fits all async IO primitive, the intention behind the Decoder interface is to not be opinionated about where the bytes are coming from. This is similar to the AsyncFileReader trait we have for parquet, which similarly is not opinionated about what the underlying IO primitive actually is.



-- 
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: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org