<?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/233596#M195419</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;You could the RouteOnAttribute processor. The SplitJson processor writes two attributes to each flow file that can be used to know when the last split flow file reaches the RouteOnAttribute file.  fragment.count = The number of split FlowFiles generated from the parent FlowFile and fragment.index = A one-up number that indicates the ordering of the split FlowFiles that were created from a single parent FlowFile (this value starts at 0 for the first flow file) , so in your case, the last flow file would have fragment.index value of 5. So, you could use the expression language to determine when the last flow file arrived to the RouteOnAttribute processor.&lt;/P&gt;&lt;P&gt;Here is an example of how you would use the fragment.count and the fragment.index attributes:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="16682-screen-shot-2017-07-04-at-41750-pm.png" style="width: 811px;"&gt;&lt;img src="https://community.cloudera.com/t5/image/serverpage/image-id/14723iBF8FEF90390C96A1/image-size/medium?v=v2&amp;amp;px=400" role="button" title="16682-screen-shot-2017-07-04-at-41750-pm.png" alt="16682-screen-shot-2017-07-04-at-41750-pm.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Any flow file where the values result in a false will be routed out the unmatched relationship. The one flow file where the result will be true is routed out the nextprocessor relationship.&lt;/P&gt;</description>
    <pubDate>Sun, 18 Aug 2019 00:12:17 GMT</pubDate>
    <dc:creator>Wynner</dc:creator>
    <dc:date>2019-08-18T00:12:17Z</dc:date>
  </channel>
</rss>

