Thanks for your interest, the IP you suggested was actually the IP it was listening on before i tried changing it to 0.0.0.0 and 127.0.0.1.   And just while writing this comment, it got resolved by using one of the custom ports 60000.   Now my question is, why is it not working on port 9090? I have checked on windows port 9090 is bound by virtualbox as expected. Inside sandbox no process is running on port 9090. Don't have any firewall in HDP and firewall on my windows is disabled.  ... View more

After you posted this new issue, I created a sample like yours, and I had the same error you have above.  Then I added the DistributedMapCacheServer, enabled it, and re-tested my flow.   I created a template for DetectDuplicate which you can find here:   https://github.com/steven-dfheinz/NiFi-Templates/blob/master/DetectDuplicate_DistributedMapCache_Demo.xml   If you install the template, you still have to + ADD the Map Cache Server in the Template's Process Group Controller Services.  The NiFI Template system does not include the server (known bug), it only includes the client.   ... View more

I am able to resolve the issue. Update nifi authorizers to use ranger ldap rather than file based.  ... View more

I solved this one, it had to do with the hdp-select, it had to be removed (and then of course clean up the yum repos) from the manager and the agents and the same hdp-select to be install on all to resolve the repo issue. ... View more

@vikrant_kumar24    1.  Yes,  sorry for some reason they didnt get saved in that version of the template.  I will update.  You should see or set it like this:   2.  Yes,  you will need to enter the Remote Url, and maybe more properties.    You also need to confirm that the json content in flow file is correct.  Mine is just an example.  I do not know what service you are connect too.  That service may require username, passwords, tokens, headers, etc.  The configuration for InvokeHttp will depend on these.   If you prefer to share more details about the service you are connecting in PM we can discuss in private.   Once you have the response from InvokeHttp,  if the response is json, you will again do EvaluateJson, grab the values you want for the new Long/Lat, and replace or overwrite the existing attributes and continue downstream with your flow.      3.  Converting CSV to JSON is pretty typical.  The CSV->JSON Method you are a working on is just fine.  You should be able to link the flowfile from that, to EvaluateJson in the flow.    My example is just a demo to show you the concepts of EvaluateJson, UpdateAttribute, and AttributesToJson.  ... View more