Implements an error processor, that acts similar to the filter processor, only that it negatively acknowledges all records passed to it. This allows the user to stop the pipeline (or send records to the DLQ) if a record matches a certain condition.
I realized we need this when we updated the webhook processor to not fail on HTTP statuses less than 500. If a user wants to still configure the pipeline to fail if the status code is for example 404, they can configure an error processor now, e.g.:
Description
Implements an
error
processor, that acts similar to thefilter
processor, only that it negatively acknowledges all records passed to it. This allows the user to stop the pipeline (or send records to the DLQ) if a record matches a certain condition.I realized we need this when we updated the webhook processor to not fail on HTTP statuses less than 500. If a user wants to still configure the pipeline to fail if the status code is for example 404, they can configure an error processor now, e.g.:
Quick checks: