apache-nifi - 在我的流程中了解 NIFI 中的通知和等待过程

Question

我是 NIFI 流程的新手，在我目前的工作中，我有通知和等待流程。有人能帮我理解这个流程吗



在什么基础上通知工作。在我的情况下，我们有 4 个模式文件进程和 4 个数据文件。
以下详细信息是通知属性..


以下是等待属性:


***我明白，等待进程在寻找 8 个信号以继续处理下一级进程。但从技术上讲，这将如何运作并不确定。

如果有人提供有关此过程的详细技术级别解释，我们将不胜感激。

Answer 1

@Andy 提到的博客很好地解释了如何一起使用等待和通知:https://ijokarumawak.github.io/nifi/2017/02/02/nifi-notify-batch/

但是，如果您想更深入地了解技术，我发现各个处理器的文档非常有用。

Description of wait

Routes incoming FlowFiles to the 'wait' relationship until a matching release signal is stored in the distributed cache from a corresponding Notify processor. When a matching release signal is identified, a waiting FlowFile is routed to the 'success' relationship, with attributes copied from the FlowFile that produced the release signal from the Notify processor. The release signal entry is then removed from the cache. Waiting FlowFiles will be routed to 'expired' if they exceed the Expiration Duration. If you need to wait for more than one signal, specify the desired number of signals via the 'Target Signal Count' property. This is particularly useful with processors that split a source FlowFile into multiple fragments, such as SplitText. In order to wait for all fragments to be processed, connect the 'original' relationship to a Wait processor, and the 'splits' relationship to a corresponding Notify processor. Configure the Notify and Wait processors to use the '${fragment.identifier}' as the value of 'Release Signal Identifier', and specify '${fragment.count}' as the value of 'Target Signal Count' in the Wait processor.It is recommended to use a prioritizer (for instance First In First Out) when using the 'wait' relationship as a loop.

Description of Notify

Caches a release signal identifier in the distributed cache, optionally along with the FlowFile's attributes. Any flow files held at a corresponding Wait processor will be released once this signal in the cache is discovered.