C++ SDK Documentation
24.2.0
|
Interface that allows storage of query-plan state, when different parts of query planning take place on different computers. More...
Public Member Functions | |
NodeSpecifyingPlanContext (ParamWriter &writer, std::vector< std::string > clusterNodes, bool canApportion) | |
NodeSpecifyingPlanContext (ParamWriter &writer, std::vector< std::string > clusterNodes, std::vector< std::string > targetNodes, bool canApportion) | |
bool | canApportionSource () const |
const std::vector< std::string > & | getClusterNodes () |
virtual ParamReader & | getReader () |
const std::vector< std::string > & | getTargetNodes () const |
virtual ParamWriter & | getWriter () |
void | setTargetNodes (const std::vector< std::string > &nodes) |
Interface that allows storage of query-plan state, when different parts of query planning take place on different computers.
For example, if some work is done on the query initiator node and some is done on each node executing the query.
In addition to the functionality provided by PlanContext, NodeSpecifyingPlanContext allows you to specify which nodes the query should run on. This is used for UDLs.
|
inline |
return whether the UDL source can be apportioned among multiple nodes or threads
|
inlineinherited |
Get a list of all of the nodes in the current cluster, by node name
Referenced by setTargetNodes().
|
inlinevirtualinherited |
Get a read-only instance of the current context
|
inline |
Return the set of nodes that this query is currently set to run on
|
inlinevirtualinherited |
Get the current context for writing
Reimplemented in Vertica::ExecutorPlanContext.
Referenced by Vertica::ExecutorPlanContext::getWriter().
|
inline |
Change the set of nodes that the query is intended to run on. Throws UnknownNodeException if any of the specified node names is not actually the name of any node in the cluster.