[ 
https://issues.apache.org/jira/browse/NIFI-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830537#comment-15830537
 ] 

ASF subversion and git services commented on NIFI-3216:
-------------------------------------------------------

Commit 7f0171ffa25bfd8932e49b3367049b101799dea4 in nifi's branch 
refs/heads/master from [~ijokarumawak]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=7f0171f ]

NIFI-3216: Add N signals to Wait/Notify

- Support counters at Wait/Notify processors so that NiFi flow can be
  configured to wait for N signals
- Extract Wait/Notify logics into WaitNotifyProtocol
- Added FragmentAttributes to manage commonly used fragment attributes
- Changed existing split processors to set 'fragment.identifier' and
  'fragment.count', so that Wait can use those to wait for all splits
get processed

This closes #1420.

Signed-off-by: Bryan Bende <[email protected]>


> Add ability to wait for N signals to Wait/Notify processors
> -----------------------------------------------------------
>
>                 Key: NIFI-3216
>                 URL: https://issues.apache.org/jira/browse/NIFI-3216
>             Project: Apache NiFi
>          Issue Type: Improvement
>    Affects Versions: 1.2.0
>            Reporter: Bryan Bende
>            Assignee: Koji Kawamura
>             Fix For: 1.2.0
>
>
> The recently added Wait and Notify processors allow a flow file to be held at 
> the Wait processor until a signal is received in the Notify processor. It 
> would be nice to be able to wait for N signals before releasing.
> One way this could be done is to have a property like "Signal Count" on the 
> Wait processor, and then count the keys in the cache starting with some 
> pattern, and release when the # of keys equals the signal count.
> This would require the ability to get all the keys from the cache, or at 
> least get all keys matching a pattern: 
> https://issues.apache.org/jira/browse/NIFI-3214



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to