You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Mark Payne (JIRA)" <ji...@apache.org> on 2015/11/30 21:21:11 UTC

[jira] [Created] (NIFI-1232) MergeContent should indicate in Provenance Event what triggered bin to be merged

Mark Payne created NIFI-1232:
--------------------------------

             Summary: MergeContent should indicate in Provenance Event what triggered bin to be merged
                 Key: NIFI-1232
                 URL: https://issues.apache.org/jira/browse/NIFI-1232
             Project: Apache NiFi
          Issue Type: Improvement
          Components: Extensions
            Reporter: Mark Payne
             Fix For: 0.5.0


We have had several e-mails on the dev@ and user@ mailing lists indicating that users do not fully understand why the MergeContent processor has chosen to bin FlowFiles together sooner than they expected. The processor should make this more obvious by indicating in the Details of the JOIN provenance event why the bin was evicted: Maximum Number of Entries Reached, Maximum Group Size Reached, Minimum Number of Entries Reached, Minimum Group Size Reached, Bin Age Expired, Maximum Number of Bins Reached.

This will allow users to much more easily understand why the MergeContent processor is behaving as it is, and allows users to more easily make adjustments to the properties if need be.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)