<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: How to wait one processor upto another processor completes its task in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/How-to-wait-one-processor-upto-another-processor-completes/m-p/233597#M195420</link>
    <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/20335/sivakarna.html" nodeid="20335" target="_blank"&gt;@siva karna&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Why not use the wait and notify processor? &lt;/P&gt;&lt;P&gt;Redirect the original file to wait processor from the splitJson processor. &lt;/P&gt;&lt;P&gt;In the wait processor set the Target Signal Count to ${fragment.count}.&lt;/P&gt;&lt;P&gt;Set the Release Signal Identifier in both the notify and wait processor to ${fragment.identifier}&lt;/P&gt;&lt;P&gt;Now start the flow. The SplitJson will split the flow file and redirect the original flow file to the wait processor. It will wait there until the target signal count i.e in this case fragment.count number of fragements have been notified by the notify processor.&lt;/P&gt;&lt;P&gt;Please try to construct a flow like below&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="17665-screen-shot-2017-07-05-at-120036-pm.png" style="width: 2346px;"&gt;&lt;img src="https://community.cloudera.com/t5/image/serverpage/image-id/14722iAE157CFB85FD6215/image-size/medium?v=v2&amp;amp;px=400" role="button" title="17665-screen-shot-2017-07-05-at-120036-pm.png" alt="17665-screen-shot-2017-07-05-at-120036-pm.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Hope this helps&lt;/P&gt;</description>
    <pubDate>Sun, 18 Aug 2019 00:12:09 GMT</pubDate>
    <dc:creator>mkalyanpur</dc:creator>
    <dc:date>2019-08-18T00:12:09Z</dc:date>
  </channel>
</rss>

