You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Sasha Krassovsky (Jira)" <ji...@apache.org> on 2022/09/24 02:42:00 UTC
[jira] [Created] (ARROW-17837) [C++] Create ExecPlan-owned QueryContext that will store a plan's shared data structures
Sasha Krassovsky created ARROW-17837:
----------------------------------------
Summary: [C++] Create ExecPlan-owned QueryContext that will store a plan's shared data structures
Key: ARROW-17837
URL: https://issues.apache.org/jira/browse/ARROW-17837
Project: Apache Arrow
Issue Type: Improvement
Reporter: Sasha Krassovsky
Assignee: Sasha Krassovsky
As we begin to include more and more plan-global stuff (such as Scheduler, AsyncScheduler, IOScheduler, ExecContext), ExecPlan's definition is becoming cluttered. ExecPlan should store and organize nodes, and store these structures elsewhere. We thus introduce QueryContext which will store any information related to the currently executing plan.
An added bonus is that now more components can be decoupled from ExecPlan and rely only on QueryContext (useful for e.g. testing, or just reusing a component in a non-ExecPlan context).
Also, this QueryContext can introduce options for the query such as maximum memory used and this legacy batching thingy.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)