You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@arrow.apache.org by "Andy Grove (Jira)" <ji...@apache.org> on 2020/04/14 16:48:00 UTC

[jira] [Assigned] (ARROW-8451) [Rust] [Datafusion] Why is DataFusion part of the Arrow repo?

     [ https://issues.apache.org/jira/browse/ARROW-8451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andy Grove reassigned ARROW-8451:
---------------------------------

    Assignee: Andy Grove

> [Rust] [Datafusion] Why is DataFusion part of the Arrow repo?
> -------------------------------------------------------------
>
>                 Key: ARROW-8451
>                 URL: https://issues.apache.org/jira/browse/ARROW-8451
>             Project: Apache Arrow
>          Issue Type: Wish
>          Components: Rust - DataFusion
>            Reporter: Remi Dettai
>            Assignee: Andy Grove
>            Priority: Minor
>
> Datafusion is a great example of how to use Arrow. But having Datafusion inside the Arrow project has several drawbacks:
>  * longer build times (rust build already slooooow)
>  * more frequent updates (creates noise)
>  * its roadmap can be quite independent of that of Arrow
> What is the actual benefit of having Datafusion inside the Arrow repo?



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