Hello Raymond,
Does the PutSQL has some number (probably 1) shown on its top right
corner in NiFi UI? If so, the execution thread is stuck at some state,
then looking at a thread dump may help to investigate where it stops.
Could you share "$NIFI_HOME/bin/nifi.sh dump" result? The output will
be
Hi
I have HDF cluster with 3 Nifi instance which lunches jobs(Hive/Spark) on
HDP cluster. Usually nifi writes all information to different repositories
available on local machine.
My question is - Does nifi writes any data,provenance information or does
spilling on HDP nodes (ex. data nodes in
Mika
And yes to question one. What you're doing us fine. There will also soon
be an option for the writer to just infer its schema from the reader which
may be useful in simplifying the config more.
Glad you are finding these useful. If you'd like to contribute a sample
flow that does this we
Answering the second question myself.
The record paths had one slash too much /bar and /foo instead of //bar
and //foo.
On 06/11/2017 10:06 PM, Mika Borner wrote:
Hi
Been playing with the new record processors (great so far!). Now I
have two questions about usage.
1. Let's say I have an
Hi
Been playing with the new record processors (great so far!). Now I have
two questions about usage.
1. Let's say I have an Update Record processor with a GrokReader and a
JsonRecordSetWriter manipulating the record. This works fine. Now I want
to further process the records with a
Apache NiFi PMC would like to announce the discovery and resolution of
CVE-2017-7667 and CVE-2017-7665. These issues have been resolved and new
versions of the Apache NiFi project were released in accordance with the
Apache Release Process.
Fixed in Apache NiFi 0.7.4 and 1.3.0
CVE-2017-7667:
