Brendan created NIFI-10041:
------------------------------
Summary: Notify/Wait Identifiers and Handling
Key: NIFI-10041
URL: https://issues.apache.org/jira/browse/NIFI-10041
Project: Apache NiFi
Issue Type: Improvement
Reporter: Brendan
As a developer there are cases where you would like to either use a generic
signal identifier so that they can be sent and trigger a wait without needing
it to be unique. There is 2 ways this could ideally be done...
1) use a generic signal with normal text and nothing unique per flow like this
"release_signal_email" and anywhere in the system using the same cache the wait
processor will pick this up. The issue with this is if your signals happen to
fast and you are passing attributes the attributes of the first release could
be overwritten because the cache was updated before the wait released the first
file and got its attributes and ideally you want the unique attributes from the
notify processors rather than multiple flows with same attributes.
2) use a unique notify signal like "1235_release_signal" where the numbers are
generated or a GUID and have the ability to use either regex or wild cards on
the wait processors signal identifier where you have "*_release_signal" where
the text is identifing fixed info but the preceding identifier makes it unique
and the wait processor will pick up all cache entires with the text
"_release_signal" this would allow you to push unique entries to the cache and
the wait processor will fetch each with attributes uniquely still
this will allow you to use the notify wait for cases where you dont want to
send the flow of the notify to the wait processor in cases that it is not
necessary to do so.
this is related in some ways and in tandem to request #NIFI-10040
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
