Member since
08-30-2016
11
Posts
4
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2794 | 08-31-2016 12:38 PM |
09-13-2016
10:04 AM
Thanks for the suggestions @Pierre Villard. I don't want to stop the processor , i want the processor to run but dont call the same url again and again. There will be list of urls will be passed to invokehttp processor and i want this processor to call url only once. Is there any way i can tell the processor that the response for this url has come so dont call it again , wait for next url and call it, if there is no urls then stop the processor.
... View more
09-13-2016
07:14 AM
2 Kudos
Hi, i'm working on creating a flow like below. InvokeHttp -> EvaluateJsonPath -> InvokeHttp -> Log The first InvokeHttp processor will call a url and run a cron job and once the cron gets started the response from server will be a job id. EvaluateJsonPath will fetch the job id from the response. Second InvokeHttp processor will take the job id and call the url to check whether the cron job has completed or not. I want to create a processor just to wait for couple of minutes/seconds before passing on to the next processor as the cron job takes some time to finish. How can i achieve this in NIFI?
... View more
Labels:
- Labels:
-
Apache NiFi
09-13-2016
07:02 AM
1 Kudo
Hi, I'm trying to call a url using invokehttp processor using POST method , which will basically inserts some data into the database. The processor is working fine and but it is repeatedly calling the url which is making the data insertion fail due to duplicates issue and also increasing the network traffic. Is there any way i can configure in the processor that once the response from the url comes then stop calling the url again?.
... View more
Labels:
- Labels:
-
Apache NiFi
09-01-2016
03:54 PM
Matt, could you please answer to this question also, https://community.hortonworks.com/questions/54481/how-to-add-request-headers-and-request-body-to-the.html
... View more
09-01-2016
03:53 PM
I have tried to delete the attribute from UpdateAttribute processor but it didn't delete it and also i tried to use AttributesToJson processor, expected only the attributes( which i specified in the attributes list) as a json but it gave me the whole attributes as a json. The behaviour of each processor is quite confusing and its not that user friendly in terms of configuring and using.
... View more
09-01-2016
01:53 PM
Hi, I'm trying to invoke a http post using invokehttp processor, the post request needs 2 things as part of headers, one is mime type and another one auth key, how can i set these parameters part of headers and also i have json to be send a request body, how can i do that.
... View more
Labels:
- Labels:
-
Apache NiFi
09-01-2016
01:50 PM
Can someone please give a working example of how processors work in nifi. What will be the output from one processor to another processor during the flow and how well we can access the floe attributes and flow content.
... View more
Labels:
- Labels:
-
Apache NiFi
08-31-2016
12:38 PM
1 Kudo
I found the problem, the fetchelasticsearch gives error if you give the default port(9200) , it doesn't matter with the port on which the elasticsearch is running. I started my elasticsearch in default port and gave the port as 9300 in fetchelasticsearch processor, worked 🙂
... View more
08-30-2016
06:53 AM
@Matt Burgess, @Pierre Villard - could you please help me with this
... View more
08-30-2016
06:40 AM
I'm getting strange error while running the FetchElasticSearch processor, below is the error. FetchElasticsearch[id=f2b2fee3-b940-4a73-8a28-0436e765c9a2] Failed to read into Elasticsearch due to None of the configured nodes are available: [{#transport#-1}{127.0.0.1}{localhost/127.0.0.1:9500}], this may indicate an error in configuration (hosts, username/password, etc.). Routing to retry: NoNodeAvailableException[None of the configured nodes are available: [{#transport#-1}{127.0.0.1}{localhost/127.0.0.1:9500}]]
2016-08-30 11:58:17,930 ERROR [Timer-Driven Process Thread-3] o.a.n.p.elasticsearch.FetchElasticsearch
org.elasticsearch.client.transport.NoNodeAvailableException: None of the configured nodes are available: [{#transport#-1}{127.0.0.1}{localhost/127.0.0.1:9500}]
at org.elasticsearch.client.transport.TransportClientNodesService.ensureNodesAreAvailable(TransportClientNodesService.java:290) ~[elasticsearch-2.1.0.jar:2.1.0]
at org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:207) ~[elasticsearch-2.1.0.jar:2.1.0]
at org.elasticsearch.client.transport.support.TransportProxyClient.execute(TransportProxyClient.java:55) ~[elasticsearch-2.1.0.jar:2.1.0]
at org.elasticsearch.client.transport.TransportClient.doExecute(TransportClient.java:283) ~[elasticsearch-2.1.0.jar:2.1.0]
at org.elasticsearch.client.support.AbstractClient.execute(AbstractClient.java:347) ~[elasticsearch-2.1.0.jar:2.1.0]
at org.elasticsearch.action.ActionRequestBuilder.execute(ActionRequestBuilder.java:85) ~[elasticsearch-2.1.0.jar:2.1.0]
at org.elasticsearch.action.ActionRequestBuilder.execute(ActionRequestBuilder.java:59) ~[elasticsearch-2.1.0.jar:2.1.0]
at org.apache.nifi.processors.elasticsearch.FetchElasticsearch.onTrigger(FetchElasticsearch.java:164) ~[nifi-elasticsearch-processors-0.7.0.jar:0.7.0]
at org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27) [nifi-api-0.7.0.jar:0.7.0]
at org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1054) [nifi-framework-core-0.7.0.jar:0.7.0]
at org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136) [nifi-framework-core-0.7.0.jar:0.7.0]
at org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47) [nifi-framework-core-0.7.0.jar:0.7.0]
at org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:127) [nifi-framework-core-0.7.0.jar:0.7.0]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_91]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [na:1.8.0_91]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_91]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [na:1.8.0_91]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_91]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_91]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_91] ElasticSearch configurations are : Host : localhost port : 9500 not sure about the root cause of the problem, do the needful.
... View more
Labels:
- Labels:
-
Apache NiFi