Hi,
To answer to your question, Nifi has a context logger which is mapped to
logback.xml file. Generally INFO level of log is defaulted in nifi-app.logs.
In your code, you can simple use getLogger().debug("your message") or INFO,
ERROR,WARN etc to enable the logging into nifi-app.log with
Hello All,
We are using NIFI 1.5 for one of the client. Seems like Listfile is super slow
when it scan a directory hosted on NFS mount.
Performance on `ls` seems to be around 200 files/sec. But Listfile takes 20
mins to list 200 files.
Is there any known issue or custom settings need to be
It depends which processor you are using...
With ListenHttp you can send "filename" as a header.
With HandleHttpRequest all the headers get added as attributes
starting with "http.headers." so if you sent "filename"
as a header you'd have "http.headers.filename" and if you needed to
move it to
Bryan,
I mean the file extension is lost.
Thanks and Regards,
Rajesh Biswas | +91 9886433461 | www.bridgera.com
-Original Message-
From: Bryan Bende [mailto:bbe...@gmail.com]
Sent: Thursday, September 20, 2018 7:08 PM
To: dev@nifi.apache.org
Subject: Re: Suggestion required HTTP and S3
nested exception is
org.apache.nifi.authorization.exception.AuthorizerCreationException:
org.apache.nifi.authorization.exception.AuthorizerCreationException: Unable
to locate node CN=ohlvnfiap004dd.oh.dev.dat.aws.vz-connect.net, OU=NIFI to
seed policies.
This means
Hello,
I'm not sure what you mean by "upload the actual image file" ?
A flow file is made up of attributes and content, and the content is
just bytes which can be anything.
If you make a POST to an end-point provided by ListenHTTP or
HandleHttpRequest, and you send the image in the body of the
Hello Bryan,
We started implanting the requirement based on your suggestion, but we faced
below issues:
1. Can we upload the actual image file instead of the flow-file that nifi
creates?
(It is more like, can we convert the flow-file into its original format. i.e.
jpg, jpeg,png etc)
2. Every
I deleted the authorizations.xml and user.xml files on all the nodes of the
cluster and restarted the nodes.
The Nifi nodes do not start up and I see the following errors int he logs
now:-
2018-09-20 08:20:09,003 ERROR [NiFi logging handler] org.apache.nifi.StdErr
Failed to start web server:
We have no wild cards in the certificates created.Each node certificate has a
unique CN name same as that of the hostname.
--
Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/
Thanks for the suggestions.
I tried exactly the same step and deleted authorizations.xml and user.xml
from all the cluster nodes and tried starting the nodes.I am encountering
the below error while starting the nodes now and the node does not start
now.
2018-09-20 08:20:09,003 ERROR [NiFi
10 matches
Mail list logo
