You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Andy Grove (Jira)" <ji...@apache.org> on 2020/12/24 18:57:00 UTC

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

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

Andy Grove commented on ARROW-10900:
------------------------------------

I added Remi to the contributors role in Jira and assigned this issue to him

> [Rust][DataFusion] Resolve TableScan provider eagerly
> -----------------------------------------------------
>
>                 Key: ARROW-10900
>                 URL: https://issues.apache.org/jira/browse/ARROW-10900
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: Rust - DataFusion
>            Reporter: Remi Dettai
>            Assignee: Remi Dettai
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.0.0
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> 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)