[
https://issues.apache.org/jira/browse/ARROW-6691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Grove updated ARROW-6691:
------------------------------
Description: 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. (was: The current implementation of the physical query plan
uses "thread::spawn" which is expensive. We should switch to using Futures and
tokio so that we are launching tasks in a thread pool instead.)
> [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
> Priority: Major
> Fix For: 1.0.0
>
>
> 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)
