[
https://issues.apache.org/jira/browse/NIFI-4658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16278591#comment-16278591
]
Brian Ghigiarelli commented on NIFI-4658:
-----------------------------------------
Thanks for the suggestion, [~joewitt] ! Does that approach still work if we're
using a Defragment merge strategy, though? From my understanding, Defragment
uses the fragment.count, fragment.identifier, and fragment.index fields, which
would all be removed / corrupted after the first MergeContent processor.
Perhaps this next question is better suited for the dev / user mailing list...
To get to a more concrete use case, my goal is to split a file (e.g., by line),
process each line, then have something (MergeContent or otherwise) take an
action once all splits of the original file have completed. My idea was to use
MergeContent to Defragment all of the splits based on fragment.count,
fragment.identifier, and fragment.index, then act on the output FlowFile
generated when all of those splits completed. Is there a better way to handle
this? Thanks for your insight!
> 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
>
> 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
(v6.4.14#64029)
