ExecuteProfilerJob allows running of Profiler Jobs with user-specified settings and provides execution results to output ports.
To be able to use this component, you need a license with Profiler and Jobflow. Also, the component requires your project is executed on CloverDX Server.
|Component||Same input metadata||Sorted inputs||Inputs||Outputs||Each to all outputs||Java||CTL||Auto-propagated metadata|
Please refer to ExecuteGraph Ports.
For the description of attributes, see ExecuteGraph Attributes. Compared to ExecuteGraph, the ExecuteProfilerJob component is missing the attributes Execution group and Skip checkConfig.
This component works similarly to ExecuteGraph. See the ExecuteGraph component documentation. For the list of main differences between these two components, see the section ExecuteProfilerJob Attributes.
The Input mapping attribute allows to override the settings of the component based on the data from the incoming token. Moreover, job parameters of the executed profiler job can be changed in the input mapping.
Input mapping is a regular CTL transformation which is executed before each profiler job execution. Input token, if any, is the only input for this mapping and outputs of the transformation are up to two records: RunConf and Parameters.
The RunConf record represents execution settings. If a field of the record is not populated by this mapping, the default value from a respective attribute of the component is used instead.
|jobURL||string||Overrides component attribute Profiler Job URL.|
Overrides the profiled data source. In case a file or an XLS spreadsheet is profiled, it will change which file is profiled. In case of a DB table job, it will override the table from which the data is obtained.
|charset||string||Overrides the input encoding (charset) of the profiled data for file and XLS profiler jobs.|
|executionType||string||Overrides the component attribute Execution type.|
|timeout||long||Overrides the component attributeTimeout.|
|clusterNodeId||string||Overrides the component attribute Cluster node ID.|
|daemon||boolean||Overrides the component attribute Execute profiler job as daemon.|
Parameters record represents all external profiler job parameters of the triggered profiler job.
The Parameters record is available in the transform dialog only if the component attribute Profiler Job URL links to an existing profiler job which is used as a template for extraction of the parameters structure. Only parameters from this profiler job can be populated by input mapping, no matter which profiler job will be actually executed in runtime.
Output mapping is regular CTL transformation which is used to populate token passed to the first output port. The mapping is executed for successful profiler job executions. Up to four input data records are available for this mapping. If output mapping is empty, fields of RunStatus record are mapped to output by name.
The input RunConf token based on which profiler job was executed is not available for component usage without input connector. This is very helpful for passing through some fields from input token to output token. This record has Port 0 displayed in the Type column.
RunStatus record provides information about profiler job execution.
|runId||long||Unique identifier of the profiler job run.|
|orignalJobURL||string||Path to executed profiler job.|
|startTime||date||Time of the job execution.|
|endTime||date||Time of job finish, or null for asynchronous execution.|
|duration||long||Job execution time in milliseconds.|
Final job execution status (FINISHED_OK | ERROR | ABORTED | TIMEOUT | RUNNING for asynchronous execution).
|errException||string||Cause an exception for failed jobs only.|
|errMessage||string||Error message for failed jobs only.|
RunInfo provides additional information about the job execution, specific to profiler jobs.
|inputRecordCount||long||Number of profiled records.|
|rejectedRecordCount||long||The number of records rejected from profiling, e.g. due to parse errors.|
RunResults record provides profiling results - output values of metrics enabled on profiled fields. The results of profiling will be available only in the case of Synchronous execution and only if the current user has sandbox privileges to read the profiling results.
Metrics with structured results return values as Multivalue Fields. This includes charts, format count metrics, etc.
If you drag a