Bob
The logs you sent are for an up and running and good to go looking
Apache NiFi 1.4.0 install.
I'm wondering if your browser has some sort of proxy settings or
something that is preventing web requests from getting to NiFi.
Please try to validate the browser settings and/or bypass the browser
Hi Martin,
I assume you wanted to ask about ValidateRecord.
As you know, ValidateRecord processor emits ROUTE provenance events
with 'Details' that explains validation error.
E.g. "Records in this FlowFile were invalid for the following reasons:
; The following 1 fields were present in the
Hi Aruna,
The resulted two FlowFiles have the same contents I guess, that is the PDF
file you specified at FetchS3Object Object Key.
The flow worked as follows actually:
1. ListS3 listed two FlowFiles, Ntl_15.csv and 11500509.pdf
2. FetchS3Object is executed twice for each incoming FlowFile
2-1.
I'm still having an issue getting to the Nifi UI on Windows using Nifi 1.4.0.
I've tried a number of different things. I've tried both java 8 and 9 jvm's.
I've tried a default configuration with no security. I've tried setting it up
on different Windows servers. I was able to use Nifi on
I just ran into this as well while trying out 1.5.0-SNAPSHOT.
What is the solution where you are running nifi behind a proxy? I tried
setting nifi.web.http.host to my proxy ip but then nifi attempted to bind
to this ip address.
Hopefully I am missing something. If not any chance a config value
Hi Rotem,
You are correct, the WriteAheadProvenanceRepository returns provenance
event FlowFile UUID value differently than the default
PersistentProvenanceRepository.
Here is the lines of code that set FlowFile UUID for the provenance events.
