You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@nifi.apache.org by James McMahon <js...@gmail.com> on 2018/02/06 22:24:32 UTC
Alternative to Failure from a processor?
Good evening. I have a somewhat challenging requirement, and hope someone
in the group has tackled this before.
There are cases where a flowFile will fail to process through a processor
in my workflow. For example, an expression language representation of an
AMQP exchange does not resolve to an exchange known to the ProcessAMQP
processor. The flowFile is not sent down the Failure output - instead it
remains in the preceding queue, and it blocks all other flowfiles.
My customer wants me to modify the processor so that in such error cases,
the flowfile gets routed down an Error output path, and so does not block
the incoming pipeline. In my case, I intend to direct that output flow path
to a second instance of PublishAMQP where all the configuration parms are
hardwired to a fixed, known AMQP route for "nifi unroutable".
Can anyone tell me how to meet this requirement? Thanks in advance for any
advice.
- Jim
Re: Alternative to Failure from a processor?
Posted by Joe Witt <jo...@gmail.com>.
yep just sounds like a bug to fix. if the topic cannot be found failure is
the right path.
please file a jira. if you can submit a pr for it that would definitely
help.
thanks
joe
On Feb 6, 2018 5:24 PM, "James McMahon" <js...@gmail.com> wrote:
> Good evening. I have a somewhat challenging requirement, and hope someone
> in the group has tackled this before.
>
> There are cases where a flowFile will fail to process through a processor
> in my workflow. For example, an expression language representation of an
> AMQP exchange does not resolve to an exchange known to the ProcessAMQP
> processor. The flowFile is not sent down the Failure output - instead it
> remains in the preceding queue, and it blocks all other flowfiles.
>
> My customer wants me to modify the processor so that in such error cases,
> the flowfile gets routed down an Error output path, and so does not block
> the incoming pipeline. In my case, I intend to direct that output flow path
> to a second instance of PublishAMQP where all the configuration parms are
> hardwired to a fixed, known AMQP route for "nifi unroutable".
>
> Can anyone tell me how to meet this requirement? Thanks in advance for any
> advice.
> - Jim
>