[
https://issues.apache.org/jira/browse/NIFI-6426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mallikarjun Terdal updated NIFI-6426:
-------------------------------------
Description:
When some processors (Example : ReplaceText), throw errors, the flowFile from
upstream doesn't get routed to failure queue. It continues to reside in
upstream and the same error is thrown infinitely after the Penalty Duration has
passed until the file has been manually deleted.
This has two challenges.
# Same error message is logged in log file multiple times which is unnecessary
and can be avoided.
# Can't make use of error handling mechanism (like alerting the client via
slack or email about the error so that it can be fixed) as the flowFile which
triggers the event has got stuck in the upstream
Irrespective of whether it's a compile time or run time exception, all flow
files should be routed to downstream.
was:
When some processors (Example : ReplaceText), throw errors, the flowFile from
upstream doesn't get routed to failure queue. It continues to reside in
upstream and the same error is thrown by the processor after the Penalty
Duration has passed infinitely until the file has manually been deleted.
This has two challenges.
# The log file will log the same error for same file multiple times
# Can't make use of error handling mechanism (like alerting the client via
slack or email about the error so that it can be fixed) as the flowFile which
triggers the event has got stuck in the upstream
Irrespective of whether it's a compile time or run time exception, all flow
files should be routed to downstream.
> FlowFiles doesn't get cleared from upstream from some processors after it
> errors
> --------------------------------------------------------------------------------
>
> Key: NIFI-6426
> URL: https://issues.apache.org/jira/browse/NIFI-6426
> Project: Apache NiFi
> Issue Type: Bug
> Environment: I'm using NiFi 1.8.0 version
> Reporter: Mallikarjun Terdal
> Priority: Minor
> Attachments: NiFiError.png
>
>
> When some processors (Example : ReplaceText), throw errors, the flowFile from
> upstream doesn't get routed to failure queue. It continues to reside in
> upstream and the same error is thrown infinitely after the Penalty Duration
> has passed until the file has been manually deleted.
> This has two challenges.
> # Same error message is logged in log file multiple times which is
> unnecessary and can be avoided.
> # Can't make use of error handling mechanism (like alerting the client via
> slack or email about the error so that it can be fixed) as the flowFile which
> triggers the event has got stuck in the upstream
> Irrespective of whether it's a compile time or run time exception, all flow
> files should be routed to downstream.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
