[
https://issues.apache.org/jira/browse/NIFI-4658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16423329#comment-16423329
]
ASF subversion and git services commented on NIFI-4658:
-------------------------------------------------------
Commit c59b6fdf66a33b68a6dd6a0a2b1da90cd98d9825 in nifi's branch
refs/heads/master from [~markbean]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=c59b6fd ]
NIFI-4658 set Maximum Number of Entries to required and allow FlowFiles having
fragment.count greater than Max Entries property
Signed-off-by: Mike Moser <mose...@apache.org>
This closes #2559
> 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)
