[
https://issues.apache.org/jira/browse/NIFI-7698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17268159#comment-17268159
]
Mark Payne commented on NIFI-7698:
----------------------------------
Rather than adding to the Provenance Details, added a FlowFile attribute. This
is more beneficial, as a RouteOnAttribute could be used, for routing bins that
timeout, for example.
> MergeContent should include Details in provenance event indicating why bin
> was merged
> -------------------------------------------------------------------------------------
>
> Key: NIFI-7698
> URL: https://issues.apache.org/jira/browse/NIFI-7698
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.13.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> MergeContent has many different configuration options. There are options for
> the minimum number of objects/bytes, and the maximum number of objects/bytes.
> There's an option for the maximum amount of time that a bin can last before
> being merged. There's also a maximum number of bins, and if that number is
> exceeded, a bin is evicted prematurely. As a result, MergeContent sometimes
> merges bins when users do not expect this to happen. Unfortunately, it does
> so without indicating why the bin was merged. When FlowFiles are merged, the
> Provenance Event should contain extra details indicating the reason that the
> bin was merged:
> - Bin Expiration Time was reached
> - Maximum number of objects was reached
> - Maximum number of bytes were reached
> - Minimum number of objects reached but not maximum
> - Minimum number of bytes reached but not maximum
> - FlowFile did not fit in any bin, and maximum number of bins reached
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
