nifi-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Sebastien Vachon <>
Subject Re: Question on MergeContent "Max bin age"
Date Fri, 09 Aug 2019 17:23:15 GMT
I created for this.

Let me know if you need more information
From: Jean-Sebastien Vachon <>
Sent: Friday, August 9, 2019 1:11 PM
To: <>
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 <>
Sent: Friday, August 9, 2019 11:43 AM
To: <>
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 <<>>
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

On Aug 9, 2019, at 8:20 AM, Jean-Sebastien Vachon <<>>

Hi all,

Is there a way to know if a MergeContent module has timed out because it reached the "Max
bin age" setting?


View raw message