[jira] [Commented] (NIFI-9562) Add archive conflict resolution strategy to PutFile

["Mark Bean (Jira)" <ji...@apache.org>]

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

Mark Bean commented on NIFI-9562:
---------------------------------

Canceling this ticket. There are alternatives to this approach. And, in a clustered environment, the use case breaks down because it would needless duplicate archived files on every node.

 

> Add archive conflict resolution strategy to PutFile
> ---------------------------------------------------
>
>                 Key: NIFI-9562
>                 URL: https://issues.apache.org/jira/browse/NIFI-9562
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Mark Bean
>            Assignee: Mark Bean
>            Priority: Major
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> The PutFile processor would benefit from an 'archive' Conflict Resolution Strategy. This strategy is similar to 'replace'. However, if a file exists on the file system and would otherwise be overwritten (or cause the FlowFile to fail), the existing file is moved to an archive directory specified by the processor's configuration.
> The processor will add the following properties which depend on the replacement strategy value of "archive" (new).
> Archive Directory
> Archive Filename Extension
> Maximum Archive File Count
> Guarantee Archive Filename Uniqueness
> The processor will (optionally) add an extension to the filename when moving it to the archive directory. If that filename is still not unique, the filename can be made unique by adding a distinct value such as UUID. Similar to the regular directory location for PutFile, the archive directory may also have a limit on the total number of files it will hold.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)