<?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: Is it possible for ExecuteStreamCommand to run a long running process? in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-it-possible-for-ExecuteStreamCommand-to-run-a-long/m-p/148087#M48574</link>
    <description>&lt;P&gt;There is not such a mechanism in place for ExecuteStreamCommand.  ExecuteProcess does have the ability to batch but based on your mention of incoming event rate, seems like the need for handling input which ExecuteProcess does not provide.&lt;/P&gt;&lt;P&gt;Depending on the nature of your parsing/process, it may be possible to convert this to use InvokeScriptedProcessor which could tie said parser/process to the component lifecycle.&lt;/P&gt;</description>
    <pubDate>Tue, 13 Dec 2016 00:34:56 GMT</pubDate>
    <dc:creator>apiri</dc:creator>
    <dc:date>2016-12-13T00:34:56Z</dc:date>
    <item>
      <title>Is it possible for ExecuteStreamCommand to run a long running process?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-it-possible-for-ExecuteStreamCommand-to-run-a-long/m-p/148085#M48572</link>
      <description>&lt;P&gt;I have a very high incoming event rate and a parser written in Python. I'm able to run it with ExecuteStreamCommand, but the latency for starting/stopping a process for every incoming FlowFile is too high and I cant' keep up with my source.&lt;/P&gt;&lt;P&gt;Is it possible for ExecuteStreamCommand to keep the external process alive and pass new FlowFiles after some signal?&lt;/P&gt;</description>
      <pubDate>Mon, 12 Dec 2016 14:51:47 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-it-possible-for-ExecuteStreamCommand-to-run-a-long/m-p/148085#M48572</guid>
      <dc:creator>rgelhausen</dc:creator>
      <dc:date>2016-12-12T14:51:47Z</dc:date>
    </item>
    <item>
      <title>Re: Is it possible for ExecuteStreamCommand to run a long running process?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-it-possible-for-ExecuteStreamCommand-to-run-a-long/m-p/148086#M48573</link>
      <description>&lt;P&gt;Hi @Randy Gelhausen,&lt;/P&gt;&lt;P&gt;Is that parser written in Python using any specific module which is not supported by Jython? If parser is completely compatible with Jython, then "ExecuteScript" processor would work without overhead of spawning a new process for every incoming flowfile.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Dec 2016 23:35:38 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-it-possible-for-ExecuteStreamCommand-to-run-a-long/m-p/148086#M48573</guid>
      <dc:creator>ninad_patkhedka</dc:creator>
      <dc:date>2016-12-12T23:35:38Z</dc:date>
    </item>
    <item>
      <title>Re: Is it possible for ExecuteStreamCommand to run a long running process?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-it-possible-for-ExecuteStreamCommand-to-run-a-long/m-p/148087#M48574</link>
      <description>&lt;P&gt;There is not such a mechanism in place for ExecuteStreamCommand.  ExecuteProcess does have the ability to batch but based on your mention of incoming event rate, seems like the need for handling input which ExecuteProcess does not provide.&lt;/P&gt;&lt;P&gt;Depending on the nature of your parsing/process, it may be possible to convert this to use InvokeScriptedProcessor which could tie said parser/process to the component lifecycle.&lt;/P&gt;</description>
      <pubDate>Tue, 13 Dec 2016 00:34:56 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-it-possible-for-ExecuteStreamCommand-to-run-a-long/m-p/148087#M48574</guid>
      <dc:creator>apiri</dc:creator>
      <dc:date>2016-12-13T00:34:56Z</dc:date>
    </item>
  </channel>
</rss>

