<?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: NiFi processor timeout - calling API in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-processor-timeout-calling-API/m-p/150477#M40581</link>
    <description>&lt;P&gt;Hi &lt;A rel="user" href="https://community.cloudera.com/users/3584/rcicak.html" nodeid="3584"&gt;@Ryan Cicak&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Several processors that call an API (if not all) have a property Connection Timeout. You can set this property to wait for a fixed duration depending on your data source, network condition and so on (look at GetHttp for instance).&lt;/P&gt;&lt;P&gt;You can use this property with a max retry strategy. The processor wait until the time out expire, and try again until it reaches a max retry number. If the max retry is reached, the flowfile goes into a processor that handle this special case (alert an admin, store data in a dir for errors, etc)&lt;/P&gt;</description>
    <pubDate>Wed, 14 Sep 2016 12:25:04 GMT</pubDate>
    <dc:creator>ahadjidj</dc:creator>
    <dc:date>2016-09-14T12:25:04Z</dc:date>
    <item>
      <title>NiFi processor timeout - calling API</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-processor-timeout-calling-API/m-p/150476#M40580</link>
      <description>&lt;P&gt;When utilizing a processor that calls an external API call, is there a way to set a timeout (for example if the API never responds) wait for 1 minute (max).  &lt;/P&gt;&lt;P&gt;Would the processor just continue to wait for a response?&lt;/P&gt;</description>
      <pubDate>Wed, 14 Sep 2016 10:12:52 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-processor-timeout-calling-API/m-p/150476#M40580</guid>
      <dc:creator>RyanCicak</dc:creator>
      <dc:date>2016-09-14T10:12:52Z</dc:date>
    </item>
    <item>
      <title>Re: NiFi processor timeout - calling API</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-processor-timeout-calling-API/m-p/150477#M40581</link>
      <description>&lt;P&gt;Hi &lt;A rel="user" href="https://community.cloudera.com/users/3584/rcicak.html" nodeid="3584"&gt;@Ryan Cicak&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Several processors that call an API (if not all) have a property Connection Timeout. You can set this property to wait for a fixed duration depending on your data source, network condition and so on (look at GetHttp for instance).&lt;/P&gt;&lt;P&gt;You can use this property with a max retry strategy. The processor wait until the time out expire, and try again until it reaches a max retry number. If the max retry is reached, the flowfile goes into a processor that handle this special case (alert an admin, store data in a dir for errors, etc)&lt;/P&gt;</description>
      <pubDate>Wed, 14 Sep 2016 12:25:04 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-processor-timeout-calling-API/m-p/150477#M40581</guid>
      <dc:creator>ahadjidj</dc:creator>
      <dc:date>2016-09-14T12:25:04Z</dc:date>
    </item>
  </channel>
</rss>

