You can configure the maximum number of load job errors at the target that a mapping task can encounter before it stops.
The error threshold can include malformed rows and data conversion errors in the load job, but the errors resulting from update, delete, or merge queries are excluded.
You can set the error threshold value in the Stop on errors session property in a mapping task. You can set the value from 0 to 2147483647. Values less than 0, alphabets, and special characters are not allowed.
When you run a mapping task with bulk operations on the target, such as delete or load data, the mapping task executes operations in parallel instead of in sequence.
The following examples describe the mapping task behavior based on the error threshold you set:
•When you set the error threshold to the maximum value of 2147483647, the mapping task continues to run even after encountering errors.
•When you set the error threshold value to 0 or 1, the mapping task stops at the first error.
•When you set the error threshold value more than 1, the mapping task continues to run until the cumulative number of errors reaches or exceeds the configured threshold value, then it stops. Since the MongoDB V2 mapping task is executed in batch mode, the cumulative number of errors might exceed the configured threshold value before the mapping task stops.
For example, consider the following scenario when you set the error threshold value to 4 in a mapping task that processes 5 batches:
- Error count 1 after processing batch 1
- Error count 2 after processing batch 2
- Error count 5 after processing batch 3
Here, the mapping task continues through batch 2 because the cumulative errors have not yet exceeded the threshold of 4. After batch 3 completes, the cumulative errors increase to 8, which exceeds the threshold, so the mapping task stops and doesn't proceed to the next batch 4 or batch 5.
You can't configure the stop on error functionality in mapping tasks that are based on mappings in advanced mode.