ile updating the
state and it worked.
On approach you suggested: does it create new controller service (with new id)
or updates the existing controller service with new state?
Thanks,
Ravi Papisetti
From: Arpit Gupta <ar...@hortonworks.com<mailto:ar...@hortonworks.com>>
Reply-To: "users
setti
From: Arpit Gupta <ar...@hortonworks.com<mailto:ar...@hortonworks.com>>
Reply-To: "users@nifi.apache.org<mailto:users@nifi.apache.org>"
<users@nifi.apache.org<mailto:users@nifi.apache.org>>
Date: Thursday, 13 July 2017 at 4:51 PM
To: "use
Hi Ravi
How are you issuing the call to enable the controller service?
One thing that could be happening is that the call to enable the controller
service is also sending the password. Response returned when you create a
controller service returns a masked password. So if this response
Each flowfile should contain a single document that gets written to elastic
search.
So if each flow file had content like
> {"DateTime": "2016-04-07 17:22:00.0", "HostName": "lab1", "CounterName":
> "AvgDiskSecTransfer", "InstanceName": "C:", "MetricValue":
> 9.60508652497083E-4}
I suspect it
Hey Philippe
Couple of things we can do to see what might be going on.
1. Check the port being used by put elastic search. Port 9200 is usually the
default http port and 9300 is the default transport port. In put elastic search
we need to use the transport port.
2. If the port is correct try
PutHDFS uses hdfs file system api to copy data to hdfs. There is no requirement
that hdfs and NiFi have to be on the same machine. PutHDFS processor asks for
the location of the core-site.xml and hdfs-site.xml which inform the file
system api’s on where to copy the data to. These config files
