[
https://issues.apache.org/jira/browse/NIFI-12882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17825424#comment-17825424
]
endzeit commented on NIFI-12882:
--------------------------------
There was a discussion on a related topic on the [dev mail
list|https://lists.apache.org/thread/bps716px66lo47x5xb7tm8znp04dgdk0] just a
few weeks ago.
> Allow control over unexpected failure behavior in processors
> ------------------------------------------------------------
>
> Key: NIFI-12882
> URL: https://issues.apache.org/jira/browse/NIFI-12882
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: saarbs
> Priority: Minor
>
> Recently we had a problem with a flow using UpdateAttribute that does
> base64decode, and one of our flow sources began sending invalid base64. This
> resulted in exceptions in the processor causing rollbacks to the flowfiles
> and backpressure in the flow.
> Since there is no failure relationship to the processor there was no way to
> resolve this issue, And we realized there are a lot of processors facing this
> issue where an unexpected failure could cause an infinite loop where some
> flows may desire to send them to a failure relationship.
> I suggest a setting or an unexpected failure relationship, which would allow
> keeping the existing behavior of a rollback but would also allow terminating
> or processing the failure in different ways.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
