If a Job has a failure, downstream Jobs will choke on that bad record and stop. Some records are written to DB, but ES indexing is not performed, nor are any other actions.
Errors in job processing have been minimal, and so this went unnoticed. Would benefit from a test.
Likely should "shunt" only good records when using a Job as input.
If a Job has a failure, downstream Jobs will choke on that bad record and stop. Some records are written to DB, but ES indexing is not performed, nor are any other actions.
Errors in job processing have been minimal, and so this went unnoticed. Would benefit from a test.
Likely should "shunt" only good records when using a Job as input.