Difference between revisions of "Execution Engine"
From Gcube Wiki
(→Execution Plan) |
|||
| Line 2: | Line 2: | ||
=Execution Plan= | =Execution Plan= | ||
For a client of the [[ExecutionEngine]] to be able to formally describe the plan that he wants to execute, the constructs offered by the Execution Plan are used. These constructs have the following main pillars. | For a client of the [[ExecutionEngine]] to be able to formally describe the plan that he wants to execute, the constructs offered by the Execution Plan are used. These constructs have the following main pillars. | ||
| − | *[[ExecutionPlan_Configuration | | + | *[[ExecutionPlan_Configuration | Configuration]] |
*:Every plan is potentially one execution unit for the execution engine. Each plan while executing can request different parametrization. | *:Every plan is potentially one execution unit for the execution engine. Each plan while executing can request different parametrization. | ||
| − | *[[ExecutionPlan_Variables | | + | *[[ExecutionPlan_Variables | Variables]] |
*:Tha variables defined in a plan are the common data placeholders through which the elements of the plan exchange data. | *:Tha variables defined in a plan are the common data placeholders through which the elements of the plan exchange data. | ||
| − | **[[ExecutionEngine_DataTypes | | + | **[[ExecutionEngine_DataTypes | Data Types]] |
**:Each variable is typed and this type describes the different characteristics of the data exchanged. | **:Each variable is typed and this type describes the different characteristics of the data exchanged. | ||
| − | **[[ExecutionPlan_Variables#Parameters | | + | **[[ExecutionPlan_Variables#Parameters | Parameters]] |
**:Each variable is accessed through defined parameters. Parameters are distinguished by their direction and processing. | **:Each variable is accessed through defined parameters. Parameters are distinguished by their direction and processing. | ||
| − | *[[ExecutionPlan_Elements | | + | ***[[ExecutionPlan_Variables#Filters | Filters]] |
| + | ***:Each parameter can provide either direct access to its underlying data or perform a number of elaborate filtering tasks before retrieving or storing data to its underlying [[ExecutionPlan_Variables#Parameters | Parameter]] and [[ExecutionEngine_DataTypes | Data Type]] | ||
| + | *[[ExecutionPlan_Elements | Execution Tree]] | ||
*:The plan hierarchy is composed of a number of elements that control the flow and the actions of the plan | *:The plan hierarchy is composed of a number of elements that control the flow and the actions of the plan | ||
| + | |||
=Execution Events= | =Execution Events= | ||
Revision as of 14:07, 10 February 2010
Invokable Profile
Execution Plan
For a client of the ExecutionEngine to be able to formally describe the plan that he wants to execute, the constructs offered by the Execution Plan are used. These constructs have the following main pillars.
- Configuration
- Every plan is potentially one execution unit for the execution engine. Each plan while executing can request different parametrization.
- Variables
- Tha variables defined in a plan are the common data placeholders through which the elements of the plan exchange data.
- Data Types
- Each variable is typed and this type describes the different characteristics of the data exchanged.
- Parameters
- Each variable is accessed through defined parameters. Parameters are distinguished by their direction and processing.
- Execution Tree
- The plan hierarchy is composed of a number of elements that control the flow and the actions of the plan
