[jira] [Commented] (NIFI-6361) PutFile doesn't check the restriction of the max files properly when replace strategy is activated

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on NIFI-6361:
-------------------------------------------------------

Commit 1975101292fcd0fceb0d30594da54e5257bc7700 in nifi's branch refs/heads/master from Andres Garagiola
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=1975101 ]

NIFI-6361: Add fix to PutFile processor

When PutFile uses 'replace' conflict resolution and max files, there is an issue when the folder has X files, and the limit is also X. The processor fails instead of replacing it, leaving X files. This commit fixes that issue.

This closes #3524.

Signed-off-by: Andres Garagiola  <an...@gmail.com>

Signed-off-by: Koji Kawamura <ij...@apache.org>


> PutFile doesn't check the restriction of the max files properly when replace strategy is activated
> --------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-6361
>                 URL: https://issues.apache.org/jira/browse/NIFI-6361
>             Project: Apache NiFi
>          Issue Type: Bug
>            Reporter: Andres Garagiola
>            Priority: Minor
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> In PutFile processor, when the conflict resolution is set to replace, the processor works in the wrong way. If we have a limit of X files in the folder, and we have already X files there. If we want to override it, the processor will fail because we exceed the number of files in the folder. Since we want to replace a file, we will not exceed the limit at all.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)