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]> 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]> > 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 > >
