You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Mark Bean (JIRA)" <ji...@apache.org> on 2018/04/03 00:07: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=16423308#comment-16423308 ] 

Mark Bean commented on NIFI-4658:
---------------------------------

[~mosermw] I put the 'throw e;' statements back in despite IntelliJ complaining. We'll address these in another PR if necessary. Also, the 'testDefragmentOldStyleAttributes()' was initially removed due to conflict with the updates made, and it is a legacy test/capability. Those changes were OBE and not necessary. So, I returned the unit test back in to TestMergeContent.

Note: I could not build with '-Pcontrib-check' due to 'Too many files with unapproved license'. I do not believe this is the case, and certainly I did not introduce any new files without licenses in this PR. Previously, I was able to overcome the RAT check with preceding the build with 'mvn clean -Pinclude-grpc' (your suggestion.) While it worked in the past, it is not working now; I still get the RAT check failure.

 

> 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)