Snapshot Job to Result 0.4
For Information on Aspire 3.1 Click Here
|Snapshot Job To Result Stage|
|Description:||Copies the job's object data into the result - plus a number of other job statistics. Used as a debugging tool, since the job's result data is usually logged or stored by feeders.|
|Inputs:||The job data|
|Outputs:||The job's result data is increased by including the job's object data.|
Object Data and Result Data
Every Job has both object data - i.e. the data being processed - and result data.
Result data is the results of processing the job. Most of the time it is "null".
However, if some stage has an error while executing the job, or decides to attach a warning message to the job, the result data will contain this information.
Result data is returned back to the feeder of the job, which will often store the result information in a file or log file somewhere so it can be examined later by administrators - especially when looking for exception errors.
Therefore, it is sometimes useful to snapshot the job object data itself into the result data. Since the result is saved for later, snapshotting the job data itself into the result provides a way to view the object data as well.
<component name="snapshotJobToResult" subType="snapshotJobToResult" factoryName="aspire-tools"/>
The result will include:
- The job status
- The job ID
- The Java class name of the job object
- The submitter ID of the job
- The parent Job ID
- Subjob statistics
- Count of sub jobs
- Number of sub jobs which returned errors
- Number of sub jobs outstanding
- The current setting for the subjob wait timeout
Plus the entire job object itself, if the job object is an AspireDocument object.