You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Joseph Witt (JIRA)" <ji...@apache.org> on 2014/12/06 17:52:12 UTC

[jira] [Commented] (NIFI-38) MergeContent should create Merged File if bin has not yet met the minimum number of entries/size but has reached a maximum number of entries/size

    [ https://issues.apache.org/jira/browse/NIFI-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14236887#comment-14236887 ] 

Joseph Witt commented on NIFI-38:
---------------------------------

verified this is already resolved in the code being imported.  Can't close tickets yet though.

> MergeContent should create Merged File if bin has not yet met the minimum number of entries/size but has reached a maximum number of entries/size
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-38
>                 URL: https://issues.apache.org/jira/browse/NIFI-38
>             Project: Apache NiFi
>          Issue Type: Bug
>            Reporter: Matt Gilman
>            Priority: Minor
>
> Current situation
> We have settings:
> Min Size: 15 MB
> Max Size: 30 MB
> Min Entries: 1
> Max Entries: 500
> Timeout: 30 mins
> We have many, many bins with 500 entries so we don't add any more. But they haven't met 15 MB min size, so they stay and wait until they timeout after 30 mins.
> If we've reached the max of 500 entries, we will never add another entry, so just go ahead and push the bin through.
> The issue here is that the Bin class's isFullEnough() can return false when isFull() returns true (ie, it's full but not full enough!). isFullEnough() should return isFull() || <current logic>



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)