I created https://issues.apache.org/jira/browse/NIFI-6537 for this.
Let me know if you need more information ________________________________ From: Jean-Sebastien Vachon <[email protected]> Sent: Friday, August 9, 2019 1:11 PM To: [email protected] <[email protected]> Subject: Re: Question on MergeContent "Max bin age" I like the idea of adding an attribute telling you what happened with your bin. People could then Route On attribute and handle different scenarios according to their own situation. However, I believe the reason should be logged somewhere as it could help people figure out what is happening to their flow. ________________________________ From: Jeff <[email protected]> Sent: Friday, August 9, 2019 11:43 AM To: [email protected] <[email protected]> Subject: Re: Question on MergeContent "Max bin age" I like the idea of seeing the details of the reason for eviction/merge in the details of a provenance event. Those same details could be provided in an attribute as well. If a log statement was also created, it should probably be at the DEBUG level. On Fri, Aug 9, 2019 at 9:57 AM Mark Payne <[email protected]<mailto:[email protected]>> wrote: I don’t believe this information is made available. It would certainly be a useful improvement to include the reason that the “bin” was evicted and merged - due to timeout, minimum threshold reached, maximum threshold reached, or due to running out of space for a new bin. Please do file a jira for that improvement. What do you think is the most useful way to relay this information? Logs? Attribute on the merged flowfile? Details of the provenance event? Thanks -Mark Sent from my iPhone On Aug 9, 2019, at 8:20 AM, Jean-Sebastien Vachon <[email protected]<mailto:[email protected]>> wrote: Hi all, Is there a way to know if a MergeContent module has timed out because it reached the "Max bin age" setting? Thanks
