Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/1644
@trixpan Sorry for the delay, I must have missed the mention on this PR.
Evaluating EL can lead to different types of Exceptions depending on the
issue with the statement (StringIndexOutOfBounds, NumberFormat, etc). If an
onTrigger throws a ProcessException, the flowfile will be penalized and the
Processor will NOT be administratively yielded. If any other type of Exception
escapes, the flowfile will be penalized and the Process will be
administratively yielded. I think the issue in this case is that we are only
catching ProcessException. As a result all other Exceptions are escaping and
causing the Processor to be yielded. I'm thinking the fix is to simply catch
Exception and then rethrow ProcessException to prevent the administrative
yielding. Thoughts?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
