[
https://issues.apache.org/jira/browse/NIFI-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15952089#comment-15952089
]
Andre F de Miranda commented on NIFI-11:
----------------------------------------
Matt,
wouldn't rolling back cause the "defective" flowfile to keep being retried? I
would imagine it would be better if we routed to Failure and moved on?
Having data we know is faulty bouncing at the same processor doesn't seem like
a good idea?
> UpdateAttribute should penalize & roll back FlowFiles for which Expression
> Language fails to evaluate
> -----------------------------------------------------------------------------------------------------
>
> Key: NIFI-11
> URL: https://issues.apache.org/jira/browse/NIFI-11
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Matt Gilman
> Assignee: Andre F de Miranda
> Priority: Minor
>
> For example, if using ${filename:substring(1, 20)} and the filename is only
> 15 characters, this will throw an Exception, which causes UpdateAttribute to
> yield and not penalize the FlowFile. Instead, it should catch this Exception
> and rollback with penalization and NOT yield, as this is a problem with the
> data, not a problem with the processor's ability to function at this moment.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)