[
https://issues.apache.org/jira/browse/ARROW-16523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Weston Pace updated ARROW-16523:
--------------------------------
Labels: acero pull-request-available (was: pull-request-available)
> [C++] Move ExecPlan scheduling into the plan
> --------------------------------------------
>
> Key: ARROW-16523
> URL: https://issues.apache.org/jira/browse/ARROW-16523
> Project: Apache Arrow
> Issue Type: Sub-task
> Components: C++
> Reporter: Weston Pace
> Assignee: Sasha Krassovsky
> Priority: Major
> Labels: acero, pull-request-available
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> Source nodes and pipeline breakers need to schedule new thread tasks. These
> tasks run entire fused pipelines (e.g. the thread task could be thought of as
> analogous to a "driver" in some other models).
> At the moment every node that needs to schedule tasks (scan node, hash-join
> node, aggregate node, etc.) handles this independently. The result is a lot
> of similar looking code and bugs like ARROW-15221 where one node takes care
> of cleanup but another doesn't.
> We can centralize this by moving this scheduling into the ExecPlan itself and
> giving nodes an ability to schedule tasks via the ExecPlan.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
