<?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 to expose a Rest service using Nifi custom processors. in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-it-possible-to-expose-a-Rest-service-using-Nifi-custom/m-p/142611#M35579</link>
    <description>&lt;P&gt;Hi &lt;A rel="user" href="https://community.cloudera.com/users/11405/ankitjain.html" nodeid="11405"&gt;@Ankit Jain&lt;/A&gt;,&lt;/P&gt;&lt;P&gt;Yes, it is possible to use NiFi to expose REST services using a processor like HandleHttpRequest. You may have a look to this blog: I used NiFi to expose a URL shortener service [1]. This is a basic example but I believe this answer your question.&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;[1] &lt;A href="https://pierrevillard.com/2016/04/10/url-shortener-service-with-apache-nifi/" target="_blank"&gt;https://pierrevillard.com/2016/04/10/url-shortener-service-with-apache-nifi/&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 22 Jul 2016 13:43:04 GMT</pubDate>
    <dc:creator>pvillard</dc:creator>
    <dc:date>2016-07-22T13:43:04Z</dc:date>
    <item>
      <title>Is it possible to expose a Rest service using Nifi custom processors.</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-it-possible-to-expose-a-Rest-service-using-Nifi-custom/m-p/142610#M35578</link>
      <description />
      <pubDate>Fri, 22 Jul 2016 13:35:05 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-it-possible-to-expose-a-Rest-service-using-Nifi-custom/m-p/142610#M35578</guid>
      <dc:creator>ankit_jain</dc:creator>
      <dc:date>2016-07-22T13:35:05Z</dc:date>
    </item>
    <item>
      <title>Re: Is it possible to expose a Rest service using Nifi custom processors.</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-it-possible-to-expose-a-Rest-service-using-Nifi-custom/m-p/142611#M35579</link>
      <description>&lt;P&gt;Hi &lt;A rel="user" href="https://community.cloudera.com/users/11405/ankitjain.html" nodeid="11405"&gt;@Ankit Jain&lt;/A&gt;,&lt;/P&gt;&lt;P&gt;Yes, it is possible to use NiFi to expose REST services using a processor like HandleHttpRequest. You may have a look to this blog: I used NiFi to expose a URL shortener service [1]. This is a basic example but I believe this answer your question.&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;[1] &lt;A href="https://pierrevillard.com/2016/04/10/url-shortener-service-with-apache-nifi/" target="_blank"&gt;https://pierrevillard.com/2016/04/10/url-shortener-service-with-apache-nifi/&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 22 Jul 2016 13:43:04 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-it-possible-to-expose-a-Rest-service-using-Nifi-custom/m-p/142611#M35579</guid>
      <dc:creator>pvillard</dc:creator>
      <dc:date>2016-07-22T13:43:04Z</dc:date>
    </item>
    <item>
      <title>Re: Is it possible to expose a Rest service using Nifi custom processors.</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-it-possible-to-expose-a-Rest-service-using-Nifi-custom/m-p/142612#M35580</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/5078/pvillard.html" nodeid="5078"&gt;@Pierre Villard&lt;/A&gt; thanks for your response. I am definitely gonna try this approach.&lt;/P&gt;</description>
      <pubDate>Fri, 22 Jul 2016 18:34:48 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-it-possible-to-expose-a-Rest-service-using-Nifi-custom/m-p/142612#M35580</guid>
      <dc:creator>ankit_jain</dc:creator>
      <dc:date>2016-07-22T18:34:48Z</dc:date>
    </item>
  </channel>
</rss>

