<?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 Scheduling ExecuteStreamCommand processor with GenerateFlowFile to run every minute in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Scheduling-ExecuteStreamCommand-processor-with/m-p/230617#M192467</link>
    <description>&lt;P&gt;I want to use ExecuteStreamCommand  to submit a spark job via the shell, and I want to use GenerateFlowFile so that I can detect the spark job failure and RouteOnAttribute as suggested by Matt's answer &lt;A href="https://community.hortonworks.com/questions/135072/how-to-handle-failure-of-nifi-executeprocess-proce.html"&gt;here&lt;/A&gt;.&lt;BR /&gt;&lt;BR /&gt;I think it worked for detecting failure, but I can't make it scheduled correctly.&lt;BR /&gt;&lt;BR /&gt;If i want the whole flow (generation of the flow file, the ExecuteStreamCommand and Routng) to be executed every 1 minute, should I schedule the GenerateFlowFile every 1 minute and leave the ExecuteStreamCommand as default (0 schedule) or should I schedule both.&lt;BR /&gt;&lt;BR /&gt;I tried different combinations but it didn't work properly, I think the GenerateFlowFile keeps generating flow files but the ExecuteStreamCommand don't run multiple times. &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;another problem is that when I stop the ExecuteStreamCommand processor, it gets stuck, I can't change its configuration and I can't stop or start it again, It didn't work again until I restart NiFi.&lt;/P&gt;&lt;P&gt;Please help. &lt;/P&gt;</description>
    <pubDate>Wed, 30 Aug 2017 04:11:25 GMT</pubDate>
    <dc:creator>MahmoudYusuf</dc:creator>
    <dc:date>2017-08-30T04:11:25Z</dc:date>
  </channel>
</rss>

