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

Posted to jira@arrow.apache.org by "Remi Dettai (Jira)" <ji...@apache.org> on 2020/12/14 11:43:00 UTC

[jira] [Created] (ARROW-10900) [Rust][DataFusion] Resolve TableScan provider eagerly

Remi Dettai created ARROW-10900:
-----------------------------------

             Summary: [Rust][DataFusion] Resolve TableScan provider eagerly
                 Key: ARROW-10900
                 URL: https://issues.apache.org/jira/browse/ARROW-10900
             Project: Apache Arrow
          Issue Type: Improvement
            Reporter: Remi Dettai


Currently, the TableScan logical plan is quite complex. It can either reference a provider or a table name that is registered to the context.

This issue is about linking the logical plan to the TableProvider directly upon parsing of the SQL. This allows to simplify greatly the code and also makes the TableScan plan easier to use by external query plan manipulations.



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