Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "SMILA/Documentation/JobParameters"
(added sample) |
m (→Example) |
||
| Line 32: | Line 32: | ||
"p1":"a" | "p1":"a" | ||
} | } | ||
| − | } | + | } |
</pre> | </pre> | ||
| Line 51: | Line 51: | ||
}, | }, | ||
... | ... | ||
| − | } | + | } |
</pre> | </pre> | ||
Revision as of 10:56, 27 May 2014
Job Parameters
The Job Manager entities can be parameterized to be configured for an actual use case.
Entities that declare parameter variables are:
Entities that initialize or set parameters are:
- Job definitions
- Workflow definitions
- Global workflow parameters
- Local action parameters
- Bucket definitions
The parameter priority increases from top to bottom, meaning that the parameters in job definitions, for example, have a lower priority than those in workflow definitions.
Workflow definitions are special entities in as far as they allow you to define general parameters in the global workflow section and worker-specific parameters in local action sections. It is important to know that the latter do not affect the buckets that the respective worker is using. As a consequence, parameters declared in a data object type can only be initialized using global workflow parameters or job parameters alternatively.
Example
Job:
{
"name":"...",
"workflow":"...",
"parameters":{
"p1":"a"
}
}
Workflow:
{
"name":"...",
"parameters":{
"p1":"b" // global workflow param, overwrites "a" from job def
},
...
"actions":[
...
{
"worker":"...",
"parameters":{
"p1":"c" // lokal workflow param, overwrites "b" from global
},
...
}