NiFi getHTTP or invokeHTTP which processor to use?












0















I have following two scenario and for each one I need recommendation as to which NiFi processor to use:




  1. I have Restful web services running outside NiFi. NiFi would like to get/post/delete/update some data by calling specific restful API. Once the Restful API receives request from NiFi it sends back the response to NiFi. Which NiFi processor to use here?


  2. In 2nd scenario, I have an application running outside NiFi. This application has its own GUI. The user need some information so he want to send request to NiFi. In NiFi, is there any processor which accepts request from application, process the request, and sends response back?



I actually read all the question with getHTTP and invokeHTTP.



I have initially tried with invokeHTTP processor. I tried both get and post call using invokeHTTP. But I don't see any response from Restful API running outside NiFi.



I did not try getHTTP.



I am using NiFi. NiFi do not have code.



I expect NiFi should be able to call Restful API running outside. I expect NiFi should accept request coming from application running outside and process that request.










share|improve this question





























    0















    I have following two scenario and for each one I need recommendation as to which NiFi processor to use:




    1. I have Restful web services running outside NiFi. NiFi would like to get/post/delete/update some data by calling specific restful API. Once the Restful API receives request from NiFi it sends back the response to NiFi. Which NiFi processor to use here?


    2. In 2nd scenario, I have an application running outside NiFi. This application has its own GUI. The user need some information so he want to send request to NiFi. In NiFi, is there any processor which accepts request from application, process the request, and sends response back?



    I actually read all the question with getHTTP and invokeHTTP.



    I have initially tried with invokeHTTP processor. I tried both get and post call using invokeHTTP. But I don't see any response from Restful API running outside NiFi.



    I did not try getHTTP.



    I am using NiFi. NiFi do not have code.



    I expect NiFi should be able to call Restful API running outside. I expect NiFi should accept request coming from application running outside and process that request.










    share|improve this question



























      0












      0








      0








      I have following two scenario and for each one I need recommendation as to which NiFi processor to use:




      1. I have Restful web services running outside NiFi. NiFi would like to get/post/delete/update some data by calling specific restful API. Once the Restful API receives request from NiFi it sends back the response to NiFi. Which NiFi processor to use here?


      2. In 2nd scenario, I have an application running outside NiFi. This application has its own GUI. The user need some information so he want to send request to NiFi. In NiFi, is there any processor which accepts request from application, process the request, and sends response back?



      I actually read all the question with getHTTP and invokeHTTP.



      I have initially tried with invokeHTTP processor. I tried both get and post call using invokeHTTP. But I don't see any response from Restful API running outside NiFi.



      I did not try getHTTP.



      I am using NiFi. NiFi do not have code.



      I expect NiFi should be able to call Restful API running outside. I expect NiFi should accept request coming from application running outside and process that request.










      share|improve this question
















      I have following two scenario and for each one I need recommendation as to which NiFi processor to use:




      1. I have Restful web services running outside NiFi. NiFi would like to get/post/delete/update some data by calling specific restful API. Once the Restful API receives request from NiFi it sends back the response to NiFi. Which NiFi processor to use here?


      2. In 2nd scenario, I have an application running outside NiFi. This application has its own GUI. The user need some information so he want to send request to NiFi. In NiFi, is there any processor which accepts request from application, process the request, and sends response back?



      I actually read all the question with getHTTP and invokeHTTP.



      I have initially tried with invokeHTTP processor. I tried both get and post call using invokeHTTP. But I don't see any response from Restful API running outside NiFi.



      I did not try getHTTP.



      I am using NiFi. NiFi do not have code.



      I expect NiFi should be able to call Restful API running outside. I expect NiFi should accept request coming from application running outside and process that request.







      apache-nifi






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jan 3 at 18:40









      James Z

      11.2k71936




      11.2k71936










      asked Jan 3 at 11:09









      Yeshwant KAKADYeshwant KAKAD

      699




      699
























          1 Answer
          1






          active

          oldest

          votes


















          3














          Yep, NiFi comes bundled with processors that satisfy both of your requirements.




          1. For scenario #1, you can use either a combination of GetHTTP/PostHTTP which as their name implies are HTTP clients that make GET and POST calls respectively. However, later the community came up with InvokeHTTP that offers more features like support for NiFi Expression Language, support for incoming flowfiles, etc.,


          2. For scenario #2, you can either use ListenHTTP or the combination of HandleHttpRequest/HandleHttpResponse. The later literally offers you have a more robust web-service implementation while the former is a simple web-hook kind. I haven't worked much with ListenHTTP so probably can't comment more on that.



          Having said that, for your second scenario, if your objective is to consume NiFi statistics, you can directly hit NiFi's rest api, rather than having a separate NiFi flow with web service capability.



          Useful Links




          • https://pierrevillard.com/2016/03/13/get-data-from-dropbox-using-apache-nifi/

          • https://dzone.com/articles/using-websockets-with-apache-nifi

          • https://ddewaele.github.io/http-communication-with-apache-nifi/






          share|improve this answer
























          • note: the GetHTTP does not allow an incoming relationship.

            – daggett
            Jan 3 at 12:21











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54021142%2fnifi-gethttp-or-invokehttp-which-processor-to-use%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          3














          Yep, NiFi comes bundled with processors that satisfy both of your requirements.




          1. For scenario #1, you can use either a combination of GetHTTP/PostHTTP which as their name implies are HTTP clients that make GET and POST calls respectively. However, later the community came up with InvokeHTTP that offers more features like support for NiFi Expression Language, support for incoming flowfiles, etc.,


          2. For scenario #2, you can either use ListenHTTP or the combination of HandleHttpRequest/HandleHttpResponse. The later literally offers you have a more robust web-service implementation while the former is a simple web-hook kind. I haven't worked much with ListenHTTP so probably can't comment more on that.



          Having said that, for your second scenario, if your objective is to consume NiFi statistics, you can directly hit NiFi's rest api, rather than having a separate NiFi flow with web service capability.



          Useful Links




          • https://pierrevillard.com/2016/03/13/get-data-from-dropbox-using-apache-nifi/

          • https://dzone.com/articles/using-websockets-with-apache-nifi

          • https://ddewaele.github.io/http-communication-with-apache-nifi/






          share|improve this answer
























          • note: the GetHTTP does not allow an incoming relationship.

            – daggett
            Jan 3 at 12:21
















          3














          Yep, NiFi comes bundled with processors that satisfy both of your requirements.




          1. For scenario #1, you can use either a combination of GetHTTP/PostHTTP which as their name implies are HTTP clients that make GET and POST calls respectively. However, later the community came up with InvokeHTTP that offers more features like support for NiFi Expression Language, support for incoming flowfiles, etc.,


          2. For scenario #2, you can either use ListenHTTP or the combination of HandleHttpRequest/HandleHttpResponse. The later literally offers you have a more robust web-service implementation while the former is a simple web-hook kind. I haven't worked much with ListenHTTP so probably can't comment more on that.



          Having said that, for your second scenario, if your objective is to consume NiFi statistics, you can directly hit NiFi's rest api, rather than having a separate NiFi flow with web service capability.



          Useful Links




          • https://pierrevillard.com/2016/03/13/get-data-from-dropbox-using-apache-nifi/

          • https://dzone.com/articles/using-websockets-with-apache-nifi

          • https://ddewaele.github.io/http-communication-with-apache-nifi/






          share|improve this answer
























          • note: the GetHTTP does not allow an incoming relationship.

            – daggett
            Jan 3 at 12:21














          3












          3








          3







          Yep, NiFi comes bundled with processors that satisfy both of your requirements.




          1. For scenario #1, you can use either a combination of GetHTTP/PostHTTP which as their name implies are HTTP clients that make GET and POST calls respectively. However, later the community came up with InvokeHTTP that offers more features like support for NiFi Expression Language, support for incoming flowfiles, etc.,


          2. For scenario #2, you can either use ListenHTTP or the combination of HandleHttpRequest/HandleHttpResponse. The later literally offers you have a more robust web-service implementation while the former is a simple web-hook kind. I haven't worked much with ListenHTTP so probably can't comment more on that.



          Having said that, for your second scenario, if your objective is to consume NiFi statistics, you can directly hit NiFi's rest api, rather than having a separate NiFi flow with web service capability.



          Useful Links




          • https://pierrevillard.com/2016/03/13/get-data-from-dropbox-using-apache-nifi/

          • https://dzone.com/articles/using-websockets-with-apache-nifi

          • https://ddewaele.github.io/http-communication-with-apache-nifi/






          share|improve this answer













          Yep, NiFi comes bundled with processors that satisfy both of your requirements.




          1. For scenario #1, you can use either a combination of GetHTTP/PostHTTP which as their name implies are HTTP clients that make GET and POST calls respectively. However, later the community came up with InvokeHTTP that offers more features like support for NiFi Expression Language, support for incoming flowfiles, etc.,


          2. For scenario #2, you can either use ListenHTTP or the combination of HandleHttpRequest/HandleHttpResponse. The later literally offers you have a more robust web-service implementation while the former is a simple web-hook kind. I haven't worked much with ListenHTTP so probably can't comment more on that.



          Having said that, for your second scenario, if your objective is to consume NiFi statistics, you can directly hit NiFi's rest api, rather than having a separate NiFi flow with web service capability.



          Useful Links




          • https://pierrevillard.com/2016/03/13/get-data-from-dropbox-using-apache-nifi/

          • https://dzone.com/articles/using-websockets-with-apache-nifi

          • https://ddewaele.github.io/http-communication-with-apache-nifi/







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jan 3 at 11:54









          Sivaprasanna SethuramanSivaprasanna Sethuraman

          2,52511743




          2,52511743













          • note: the GetHTTP does not allow an incoming relationship.

            – daggett
            Jan 3 at 12:21



















          • note: the GetHTTP does not allow an incoming relationship.

            – daggett
            Jan 3 at 12:21

















          note: the GetHTTP does not allow an incoming relationship.

          – daggett
          Jan 3 at 12:21





          note: the GetHTTP does not allow an incoming relationship.

          – daggett
          Jan 3 at 12:21




















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54021142%2fnifi-gethttp-or-invokehttp-which-processor-to-use%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Mossoró

          Error while reading .h5 file using the rhdf5 package in R

          Pushsharp Apns notification error: 'InvalidToken'