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 <firstname.lastname@example.org>
Sent: Friday, August 9, 2019 11:43 AM
To: email@example.com <firstname.lastname@example.org>
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.
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?
Sent from my iPhone
Is there a way to know if a MergeContent module has timed out because it reached the "Max bin age" setting?