[ https://issues.apache.org/jira/browse/ARROW-6691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17032035#comment-17032035 ]
Andy Grove commented on ARROW-6691: ----------------------------------- [~sd2k] You might be right, but given that we now have a flight server example using tokio, it seems ideal to use tokio all the way through to query execution to have a complete async implementation? I agree that this is perhaps not an ideal issue to try to take on for a new contributor though! > [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 > > 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)