Integration job parameters reference
The following table lists the parameters available to customize and optimize the execution of integration jobs.
For parameter changes to take effect, it is necessary to redeploy the model and select the Generate Jobs Definition option in the Deploy Model Edition wizard. |
Parameter name | Values | Description | ||||
---|---|---|---|---|---|---|
|
0 or 1 |
If this parameter is set to 1, consecutive SemQL enrichers are merged into a single SQL statement when executed. This applies to all entities. For more information, see Enricher aggregation. The default value for this parameter is 0. |
||||
|
0 or 1 |
If this parameter is set to 1, consecutive API enrichers are piped so that the output of an enricher is directly passed in memory to the next one. This applies to all entities. For more information, see Enricher aggregation. The default value for this parameter is 0. |
||||
|
0 or 1 |
If this parameter is set to 1, consecutive SemQL enrichers are merged into a single SQL statement when executed. This applies only to the entity whose name is provided as |
||||
|
0 or 1 |
If this parameter is set to 1, consecutive API enrichers are piped, so that the output of an enricher is directly passed in memory to the next one. This applies only to the entity whose name is provided as |
||||
|
0, 1, or JSON object |
If this parameter is set to 1, statistics collection is triggered in the data location tables to optimize processing. This option is useful to accelerate the processing of large datasets. The default value for this parameter is 1. For PostgreSQL and SQL Server, this parameter supports a JSON object to define advanced options, described in Analyzing database statistics. |
||||
|
true, false, or <job_name> |
Specify whether a post-processing job should be started after the current job for the records that reference a parent record which golden ID has changed. This new job starts in a new batch. Possible values are:
|
||||
|
true, false, or <job_name> |
Specify whether a post-processing job should be started after the current job for records of This parameter works like
|
||||
|
0 or 1 |
If this parameter is set to 1 (default value), the phase that processes possible deletions is executed. To entirely skip this phase, set this parameter to 0. In that case, deletions are not processed. |
||||
|
0 or 1 |
If this parameter is set to 0 (the default value is 1), the job phase—for data locations running on Oracle—that truncates timestamp columns representing date attributes to the date is skipped. You may want to skip this phase if this truncation is not needed. |
||||
|
0 or 1 |
If this parameter is set to 0 (the default value is 1), the job phase—for data locations running on PostgreSQL and SQL Server—that transforms empty strings to null values is skipped. You may want to skip this phase if this normalization is not needed. |
||||
|
Number |
When the API enrichers (Java plug-ins and REST clients) execution and database are fast, the network can be the bottleneck. A batch update is a group of updates sent together to the database in one batch, rather than sending the updates one by one. This JDBC batch update size is used by API enrichers when writing records to the database. A high value for this parameter reduces the number of network accesses to write the data but increases the memory load on the server. This parameter applies to API enrichers running individually. For chained API enrichers, it applies to the last enricher in the chain, which writes enriched data to the database. |
||||
|
0 or 1 |
If this parameter is set to 1, error recycling is triggered and rejects from previous job executions are recycled in this job. The default value for this parameter is 0. |
||||
|
0 or 1 |
When this parameter is set to 1, the job performs consolidation for the The default behavior is defined by |
||||
|
0 or 1 |
When this parameter is set to 1, the job performs consolidation in a single step, which strongly improves performance for high data volumes. When this parameter is set to 0, consolidation is performed in two steps (clustering and matching). This parameter applies to all entities for which no The default value for this parameter can be configured with the |