[
https://issues.apache.org/jira/browse/NIFI-6344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy LoPresto updated NIFI-6344:
--------------------------------
Labels: attribute backwards-compatibility expression-language
routing (was: )
Affects Version/s: 1.9.2
Status: Patch Available (was: Open)
> Add Failure Relationship to UpdateAttribute
> -------------------------------------------
>
> Key: NIFI-6344
> URL: https://issues.apache.org/jira/browse/NIFI-6344
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Affects Versions: 1.9.2
> Reporter: Peter Wicks
> Assignee: Peter Wicks
> Priority: Minor
> Labels: routing, attribute, expression-language,
> backwards-compatibility
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> EL makes it possible for an UpdateAttribute processor to fail. When this
> happens the FlowFile is rolled back, and there is no way to route it to
> handle the failure automatically.
> Considerations:
> UpdateAttribute is used in probably all but the simplest of flows, thus any
> change made to support a failure relationship must be handled delicately. The
> goal of this change is for users to have no change in functionality unless
> they specifically configure it.
> Proposal:
> It was proposed on the Slack channel to create the failure relationship, but
> default it to auto-terminate. This is a good start, but without further work
> would result in a change in functionality. I propose that we will default to
> auto-terminate, but also detect this behavior in the code. If the Failure
> relationship is set to auto-terminate then we will rollback the transaction.
> The only downside I see with this is you can't actually auto-terminate
> Failures without the addition of another property, such as Failure Behavior:
> Route to Failure and Rollback options.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
