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

[jira] [Assigned] (ARROW-14443) [C++] Implement Plan Fragments support for ExecPlan.

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

Neal Richardson reassigned ARROW-14443:
---------------------------------------

    Fix Version/s:     (was: 9.0.0)
         Assignee:     (was: Percy Camilo Triveño Aucahuasi)
           Labels: query-engine stop  (was: query-engine)

This issue has been inactive for 3 months, so it has been unassigned and marked as unstarted. If you are still working on this, feel free to reassign yourself and resume progress.

> [C++] 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
>            Priority: Major
>              Labels: query-engine, stop
>
> 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.20.10#820010)