Put 0 seconds to penalized and it goes to the logger processor without waiting.
That's fine. I just do not understand weel why there is a penalty or yield failure, but now that I know this, this is ok. Le lun. 10 févr. 2020 à 14:58, Etienne Jouvin <[email protected]> a écrit : > Mark, > > Hum fine, I was looking the source code and touch this point ;) > > Thanks a lot. > I am going to play with that. > > Etienne > > > Le lun. 10 févr. 2020 à 14:55, Mark Payne <[email protected]> a écrit : > >> Etienne, >> >> When a FlowFile fails, ExecuteSQL penalizes the FlowFile. This allows you >> to loop failures without constantly hitting the database. By default, the >> FlowFile will be penalized for 60 seconds. See [1] for more information on >> how penalization works and how to configure the penalty duration. >> >> Thanks >> -Mark >> >> [1] >> http://nifi.apache.org/docs/nifi-docs/html/user-guide.html#settings-tab >> >> > On Feb 10, 2020, at 8:47 AM, Etienne Jouvin <[email protected]> >> wrote: >> > >> > Hello All. >> > >> > Here is an extract of my process >> > <image.png> >> > >> > If the executeSQL failed (invalid SQL for example), the flowfile goes >> to the failure relation. >> > At very first, I call the update attribute and I saw that the flowfile >> is kept into the relation, never proceeded. >> > So I try to put intermediate processor, LogMessage, but this is the >> same. >> > >> > Notice that I do not have this in the success relation. >> > >> > Does someone have this also ? >> > >> > Regards >> > >> > Etienne Jouvin >> > >> >>
