[
https://issues.apache.org/jira/browse/NIFI-6537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Sebastien Vachon resolved NIFI-6537.
-----------------------------------------
Resolution: Not A Problem
You can use the "merge.count" attribute
> Provide details about why a bin was merged in a MergeContent processor
> ----------------------------------------------------------------------
>
> Key: NIFI-6537
> URL: https://issues.apache.org/jira/browse/NIFI-6537
> Project: Apache NiFi
> Issue Type: Improvement
> Affects Versions: 1.9.1
> Reporter: Jean-Sebastien Vachon
> Priority: Minor
>
> When a flow is being merged using a MergeContent processor, it would be
> useful to know why it was merged as there are quite some reasons for the
> merge to happen.
> The information could be saved in a special attribute and/or through
> different streams and should be logged somewhere as it is useful information
> to track and debug what's happening in a flow.
> In my particular case, I had trailing flows because the bin reached the "max
> bin age" threshold.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
