You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Percy Camilo Triveño Aucahuasi (Jira)" <ji...@apache.org> on 2021/10/22 17:51:00 UTC

[jira] [Updated] (ARROW-14443) Implement Plan Fragments support for ExecPlan.

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

Percy Camilo Triveño Aucahuasi updated ARROW-14443:
---------------------------------------------------
    Summary: Implement Plan Fragments support for ExecPlan.   (was: Implement Plan Fragmets support for ExecPlan. )

> Implement Plan Fragments support for ExecPlan. 
> -----------------------------------------------
>
>                 Key: ARROW-14443
>                 URL: https://issues.apache.org/jira/browse/ARROW-14443
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: C++
>            Reporter: Alexander Ocsa
>            Assignee: Percy Camilo Triveño Aucahuasi
>            Priority: Major
>              Labels: query-engine
>             Fix For: 7.0.0
>
>
> A plan fragment: Implement Plan Fragmets support for ExecPlan. A plan fragment: * Has zero or more inputs and one or more outputs
>  * Is a logical description of how the output data should be generated based on the input data.
>  * Is immutable during query runtime and can be shared and reused between queries.
> The relation between a plan fragment and a exec plan is: * An exec plan can be executed on its own.
>  * A plan fragment allows to have some inputs that are not bound to any source nodes and require some external entity to provide the data at runtime using the push interface of ExecNodes (the external entity is related to DataHolder)



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