Apparently that template doesn't actually do what it said it did. It wasn't using the "q" attribute in the URL so it was just hitting google without any query.
I just pushed out a change to the repo which fixes it to properly hit "http://www.google.com/search?q=${q}&rct=j"; where the ${q} is replace with the attribute that's created in the previous processor. The "rct=j" was just part of the url when I did manual google search in my browser and allowed me to do the search in NiFi as well. I'll be changing on Confluence as well. Sorry about that, Joe - - - - - - Joseph Percivall linkedin.com/in/Percivall e: [email protected] On Friday, December 18, 2015 3:32 PM, Burrows James A <[email protected]> wrote: Yes the HTTP call being generated is sending without the query string values. For the configuration of my InvokeHTTP I used that template, but changed the remote URL to point to my server (https://www.google.com -> http://localhost). James -----Original Message----- From: Joe Percivall [mailto:[email protected]] Sent: Friday, December 18, 2015 1:25 PM To: [email protected] Subject: [RMX:NL] Re: [RMX:NL] Re: InvokeHTTP request parameters Yeah I compiled from the wiki as well. I want to get a listing of as many templates as possible so when someone needs an example template I/we can check the excel doc to see which processors are used in which template. Still working on generating more content though. Are you saying that the HTTP call you're generating in InvokeHttp is arriving at the server without any query string values? If that's the case and you're able, can you reply with your InvokeHttp config? Joe - - - - - - Joseph Percivall linkedin.com/in/Percivall e: [email protected] On Friday, December 18, 2015 3:16 PM, Burrows James A <[email protected]> wrote: Thanks for the reply. That appears the be the same template from the wiki, and it seems like it should work, but when I get the request on the server there are no querystring values. -----Original Message----- From: Joe Percivall [mailto:[email protected]] Sent: Friday, December 18, 2015 12:58 PM To: [email protected] Subject: [RMX:NL] Re: InvokeHTTP request parameters Hello James, I'm actually working on repo that includes many different templates. There are a few that have InvokeHttp in them (can find the exact ones using the excel doc at the top level) but this is a simple one that uses InvokeHttp: https://github.com/hortonworks-gallery/nifi-templates/blob/master/templates/InvokeHttp_And_Route_Original_On_Status.xml Does that fit your use-case? Joe - - - - - - Joseph Percivall linkedin.com/in/Percivall e: [email protected] On Friday, December 18, 2015 2:52 PM, Burrows James A <[email protected]> wrote: I’m wondering if anyone has a sample, or tutorial on how to configure the InvokeHTTP request parameters. I see that you can configure the request headers using the Attributes to Send property, but I need to be able to specify the request parameters to integrate with a rest api. Thanks, James
