You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Brandon DeVries (JIRA)" <ji...@apache.org> on 2018/03/16 15:05:00 UTC
[jira] [Commented] (NIFI-4658) MergeContent Max Number of Entries
resetting to default value
[ https://issues.apache.org/jira/browse/NIFI-4658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16402019#comment-16402019 ]
Brandon DeVries commented on NIFI-4658:
---------------------------------------
So, first, it sounds like "Maximum Number of Entries" should be marked as required, since that's effectively the behavior. The lack of that explicit statement is probably the cause of a lot of the confusion.
Second, the real issue here for defragmentation seems to be the lack of communication as to what is happening / why a FlowFile fails. If "Maximum Number of Entries" is going to be required / enforced even in defragmentation mode, then the easiest thing to do is immediately fail anything incoming with a fragment.count greater than that value, with an accompanying warning indicating why the file failed ("fragment.count is greater than Maximum number of entries... defragmentation cannot succeed as configured"). We can probably use a FlowFileFilter to get and fail all of the offending files in queue whenever one is encountered during normal processing, to limit the number of warnings.
I'm still not 100% on board with the use of "Maximum Number of Entries" for defragmentation, but as long as what is happening is made clear it can be worked around...
> 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
> 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)