[
https://issues.apache.org/jira/browse/NIFI-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aldrin Piri updated NIFI-813:
-----------------------------
Description:
UpdateAttribute's genesis predates expression language, and as originally
created would have made failure improbable (impossible?) in context of typical
processing. As a result, when EL was introduced, there was also a means
wherein the processor could fail. Currently, there is no failure relationship.
As a result, the only way to remove files that are failing due to an EL issues
and placed back onto the queue is through an expiration on the incoming
connection. One particular instance is that of formatting a bad date input.
Template showing example to follow.
It could be the case this is a deficiency in just this particular EL function,
but should EL become an extension point, it is entirely conceivable that
failure cases become an occurrence that needs to be handled.
was:
UpdateAttribute's genesis predates expression language, and as originally
created would have made failure . As a result, when EL was introduced, there
was also a means wherein the processor could fail. Currently, there is no
failure relationship. As a result, the only way to remove files that are
failing due to an EL issues and placed back onto the queue is through an
expiration on the incoming connection. One particular instance is that of
formatting a bad date input. Template showing example to follow.
It could be the case this is a deficiency in just this particular EL function,
but should EL become an extension point, it is entirely conceivable that
failure cases become an occurrence that needs to be handled.
> UpdateAttribute does not have a failure relationship for handling EL failures
> -----------------------------------------------------------------------------
>
> Key: NIFI-813
> URL: https://issues.apache.org/jira/browse/NIFI-813
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework, Extensions
> Affects Versions: 0.2.1
> Reporter: Aldrin Piri
> Attachments: NIFI-813_Example.xml
>
>
> UpdateAttribute's genesis predates expression language, and as originally
> created would have made failure improbable (impossible?) in context of
> typical processing. As a result, when EL was introduced, there was also a
> means wherein the processor could fail. Currently, there is no failure
> relationship. As a result, the only way to remove files that are failing due
> to an EL issues and placed back onto the queue is through an expiration on
> the incoming connection. One particular instance is that of formatting a bad
> date input. Template showing example to follow.
> It could be the case this is a deficiency in just this particular EL
> function, but should EL become an extension point, it is entirely conceivable
> that failure cases become an occurrence that needs to be handled.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
