Andre, My understanding of that statement is that NiFi lets the user decide how to build their dataflow, and allows them to build it in a way that favors guaranteed delivery, or favors loss tolerance, depending on their needs.
I would think loss tolerance is referencing the idea of expiring data from queues after a certain threshold, and maybe terminating failure relationships. The overall point being that the user makes the decision and not the framework, which is the same motto for a lot of other parts of NiFi. -Bryan On Thu, Mar 2, 2017 at 11:54 PM, Andre <[email protected]> wrote: > All, > > A good number of NiFi related material makes the following statement about > NiFi: > > Loss tolerant vs guaranteed delivery > > I have not historically used NiFi in a loss tolerant environment but after > investigating the documentation it isn't clear to me how NiFi implements > loss tolerance? > > Are we referring to Clustering? Flow expiration? To the ability to discard > flowfiles that get piped to the REL_FAILURE relationships? etc? > > Would anyone mind shedding some light about what are we referring to when > presenting the "Loss tolerant vs guaranteed delivery" > > I thank you in advance
