<?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 DB Trigger to NiFi in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/DB-Trigger-to-NiFi/m-p/186067#M61749</link>
    <description>&lt;P&gt;We have an Oracle DB and we run nightly batch job but when that job would end varies. Now we have a NiFi workflow getting data from this Oracle DB but should not be during the batch job run. How do we turn off/on the entry point processor (say ExecuteSQL) whenever the Oracle Batch job is running/has stopped? &lt;/P&gt;&lt;P&gt;We thought of using Oracle DB trigger and then invoke a HTTP request within that trigger when the job would end, but is there a processor in NiFi where you can put up a simple web service / REST endpoint and then use that to trigger or turn on the ExecuteSQL processor?&lt;/P&gt;</description>
    <pubDate>Thu, 25 May 2017 16:46:56 GMT</pubDate>
    <dc:creator>menorah84</dc:creator>
    <dc:date>2017-05-25T16:46:56Z</dc:date>
    <item>
      <title>DB Trigger to NiFi</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/DB-Trigger-to-NiFi/m-p/186067#M61749</link>
      <description>&lt;P&gt;We have an Oracle DB and we run nightly batch job but when that job would end varies. Now we have a NiFi workflow getting data from this Oracle DB but should not be during the batch job run. How do we turn off/on the entry point processor (say ExecuteSQL) whenever the Oracle Batch job is running/has stopped? &lt;/P&gt;&lt;P&gt;We thought of using Oracle DB trigger and then invoke a HTTP request within that trigger when the job would end, but is there a processor in NiFi where you can put up a simple web service / REST endpoint and then use that to trigger or turn on the ExecuteSQL processor?&lt;/P&gt;</description>
      <pubDate>Thu, 25 May 2017 16:46:56 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/DB-Trigger-to-NiFi/m-p/186067#M61749</guid>
      <dc:creator>menorah84</dc:creator>
      <dc:date>2017-05-25T16:46:56Z</dc:date>
    </item>
    <item>
      <title>Re: DB Trigger to NiFi</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/DB-Trigger-to-NiFi/m-p/186068#M61750</link>
      <description>&lt;A rel="user" href="https://community.cloudera.com/users/1651/menorah84.html" nodeid="1651"&gt;@J. D. Bacolod&lt;/A&gt;&lt;P&gt;Anything you can do within the NiFi UI, you can also do via NiFi Rest-api calls.  So you could issue a rest-api call to stop specific processors before the batch job is started and then issue another rest-api call to start the processor again after the batch job completes.&lt;/P&gt;&lt;P&gt;&lt;A href="https://nifi.apache.org/docs/nifi-docs/rest-api/index.html" target="_blank"&gt;https://nifi.apache.org/docs/nifi-docs/rest-api/index.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Matt&lt;/P&gt;</description>
      <pubDate>Thu, 25 May 2017 19:05:18 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/DB-Trigger-to-NiFi/m-p/186068#M61750</guid>
      <dc:creator>MattWho</dc:creator>
      <dc:date>2017-05-25T19:05:18Z</dc:date>
    </item>
  </channel>
</rss>

