UpdateAttribute is a good example of a soft threshold behavior. By default,
this processor operates in micro batches of 100. So, regardless if you set
BP to e.g. 5, it will commit 100 events and then be throttled back by the
connection. A user will see 100 events in the connection even though 5
Great questions and discussion points here and I agree with your
statement about the importance of honoring back pressure targets the
user believes they set.
The way back pressure works is that before a processor is given a
thread to execute (each onTrigger cycle) the framework checks all
I have a NiFilosophical question that came up when I had a GetSFTP
processor running to a back-pressured connection.
My GetSFTP is configured with max selects = 100, and the files in the
remote directory are nearly 1GB each. The queue has a backpressure of 2GB,
and I assumed each run of GetSFTP
Hi Matt,
I am using Version: Nifi 1.0.0.
The data that I get from the getHttp request is the same as in the text
file. I just copied the content of the flowfile from the getHttp processor
to the text file.
What do you suggest i should do for the failure error?
The database that I use is MySql.
Hi Ibrahim,
I think this is a question you should address to the users mailing list as
it is more a use case question.
Anyway, once you get your files after the combination of ListSFTP and
FetchSFTP processors, your flow files will have an attribute 'filename'
with the name of your files. Then
