[
https://issues.apache.org/jira/browse/NIFI-4658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16405611#comment-16405611
]
Mark Bean commented on NIFI-4658:
---------------------------------
Again, consistent with Joe's suggestion, MergeContent now ignores Maximum
Number of Entries in defragmentation mode. Instead, fragment.count is used for
the number of fragments of the resulting merged flowfile.
Code has been committed, squashed and pushed. I believe this addresses any
comments on this ticket. The PR can be completed.
> MergeContent Max Number of Entries resetting to default value
> -------------------------------------------------------------
>
> Key: NIFI-4658
> URL: https://issues.apache.org/jira/browse/NIFI-4658
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.4.0
> Reporter: Brian Ghigiarelli
> Assignee: Mark Bean
> Priority: Major
>
> Prior to and including 1.4.0, the MergeContent processor supports a property
> called "Maximum Number of Entries". It has a default value of 1,000. Prior to
> 1.4.0 and in the description of this property, if the property is not set,
> there will be no maximum number of files to include in a bundle.
> However, with the release of 1.4.0, if you clear the value of this property
> in order to have an unlimited number of files in the bundle and "Apply" the
> change, the next time that you open the configuration of the processor, it
> will again be set to the default value of 1,000. The expectation is that the
> cleared value will remain cleared, maintaining a configuration for an
> unlimited number of files in a merge bundle.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
