A Batch Job scope has three batch steps. An event processor throws an error in the second batch step because the input data is incomplete.
What is the default behavior of the batch job after the error is thrown?
A Batch Job scope has three batch steps. An event processor throws an error in the second batch step because the input data is incomplete.
What is the default behavior of the batch job after the error is thrown?
In the context of batch job processing, the default behavior when an error is encountered in one of the batch steps is to halt the entire processing of the batch job. This is to ensure that any issues are addressed before proceeding further, thereby avoiding potential inconsistencies or data corruption. Therefore, all processing of the batch job stops if an error is thrown in any of the batch steps.
Mule has three options for handling a record-level error: Finish processing Stop the execution of the current job instance. Finish the execution of the records currently in-flight, but do not pull any more records from the queues and set the job instance into a FAILURE state. The On Complete phase is invoked. Continue processing the batch regardless of any failed records, using the acceptExpression and acceptPolicy attributes to instruct subsequent batch steps how to handle failed records. Continue processing the batch regardless of any failed records (using the acceptExpression and acceptPolicy attributes to instruct subsequent batch steps how to handle failed records), until the batch job accumulates a maximum number of failed records at which point the execution will halt just like in option 1. By default, Mule’s batch jobs follow the first error handling strategy which halts the batch instance execution. The above behavior is controlled through the maxFailedRecords attributes.
A is the correct answer
A is correct
the default is stop all execution