[
https://issues.apache.org/jira/browse/ARROW-6691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Grove closed ARROW-6691.
-----------------------------
Resolution: Invalid
I spent a little time working on a PoC of this [1] but the advice from the
Tokio team is that we are better off just using dedicated threads for file io
and just use tokio for network io, which we already do in the flight server
(thanks to Tonic) so I am closing this.
[1] https://github.com/andygrove/async-query/blob/master/src/main.rs
> [Rust] [DataFusion] Use tokio and Futures instead of spawning threads
> ---------------------------------------------------------------------
>
> Key: ARROW-6691
> URL: https://issues.apache.org/jira/browse/ARROW-6691
> Project: Apache Arrow
> Issue Type: Sub-task
> Components: Rust, Rust - DataFusion
> Reporter: Andy Grove
> Assignee: Andy Grove
> Priority: Major
> Fix For: 1.0.0
>
> Attachments: image-2019-12-07-17-54-57-862.png
>
>
> The current implementation of the physical query plan uses "thread::spawn"
> which is expensive. We should switch to using Futures, async!/await!, and
> tokio so that we are launching tasks in a thread pool instead and writing
> idiomatic Rust code with futures combinators to chain actions together.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
