Brendan created NIFI-10040:
------------------------------
Summary: Wait Processor Generate Empty Flow File on Signal Release
Key: NIFI-10040
URL: https://issues.apache.org/jira/browse/NIFI-10040
Project: Apache NiFi
Issue Type: New Feature
Reporter: Brendan
Attachments: image-2022-05-20-11-12-07-452.png
As a developer I would like to be able to use the notify/wait processor cycle
to signal an action that must happen without needing to send an input to the
wait processor. So when the wait processor receives the signal generate an
empty flow and add the attributes from the notify to the flow.
Why? in some cases you use nested processor groups for several reasons and
certain logic can be contained and reusable and it would be ideal to have that
in a single instance that can be managed on a higher level rather than
duplication while at the same time not having to route and pass flows up and
down excessively when not necessary
Example
When sending emails once can simply put Email right there with some parameters
and its done. in our case we use HTML templates with variations and store the
templates in a SimpleLookupStore and fetch that email and swap out tags with a
few attributes that are passed at that point in time.
To allow this to stand in isolation we would have to have a generate file sit
in a wait queue loop until a signal trigger happens to release the generated
file but rather that having something permanently in it would be ideal to have
a wait processor option to generate a empty flow on signal to perform the
generic steps in isolation allowing to manage changes to that pipeline or flow
in a single space.
E.g currently to achive this you would need to do something like this...
!image-2022-05-20-11-12-07-452.png!
In the event of multiple signals possible you would have to ensure you keep a
matching number of things in the queue to have enough to release accordingly
where you could just generate a flow every time a signal is received to perform
standalone tasks.
NOTE: not sure if this is a feature or improvement request.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)