You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Jorge (Jira)" <ji...@apache.org> on 2020/07/13 13:26:00 UTC

[jira] [Commented] (ARROW-9425) [Rust][DataFusion] Make ExecutionContext sharable between threads

    [ https://issues.apache.org/jira/browse/ARROW-9425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17156701#comment-17156701 ] 

Jorge commented on ARROW-9425:
------------------------------

For reference, the code to call datafusion from Python is here: [https://github.com/jorgecarleitao/datafusion-python|https://github.com/jorgecarleitao/datafusion-python] . It is very much experimental, but works as expected.


> [Rust][DataFusion] Make ExecutionContext sharable between threads
> -----------------------------------------------------------------
>
>                 Key: ARROW-9425
>                 URL: https://issues.apache.org/jira/browse/ARROW-9425
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: Rust - DataFusion
>            Reporter: Jorge
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> I have been playing with pyo3 to ship and call this library directly from Python, and the current ExecutionContext can't be used within Python with threads due to the usage of `Box<dyn TableProvider>` on `datasources`, i.e. no `Sync` nor `Send`.
> This issue likely affects integration of DataFusion with other libraries.
> I propose that we allow ExecutionContext to be sharable between threads, e.g. using {{Box<dyn TableProvider + Send + Sync>}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)