This repository has been archived by the owner on Feb 18, 2024. It is now read-only.
Added support to read Arrow streams asynchronously #832
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds support to read an arrow stream asynchronously (via
futures::AsyncRead
), thereby allowing users to use their favorite runtime to suspend reading from it when either the stream is marked as "waiting", or the reader is not ready (e.g. network).The design is equivalent to the rest of the IO in the crate. Recall that we do not separate IO-bounded from CPU-bounded ops when reading and writing to Arrow IPC because arrow IPC format has almost no CPU involved (it is reading/writing back-to-back).