[
https://issues.apache.org/jira/browse/NIFI-12928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17830625#comment-17830625
]
ASF subversion and git services commented on NIFI-12928:
--------------------------------------------------------
Commit 87196e23d651fa6edeae364c2189a7779e39060e in nifi's branch
refs/heads/support/nifi-1.x from Peter Turcsanyi
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=87196e23d6 ]
NIFI-12928 Added Simple Write strategy in PutAzureDataLakeStorage
Signed-off-by: Pierre Villard <pierre.villard...@gmail.com>
This closes #8559.
> Add Simple Write strategy in PutAzureDataLakeStorage
> ----------------------------------------------------
>
> Key: NIFI-12928
> URL: https://issues.apache.org/jira/browse/NIFI-12928
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Peter Turcsanyi
> Assignee: Peter Turcsanyi
> Priority: Minor
> Fix For: 2.0.0-M3
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> NIFI-8248 introduced temporary location for file uploads in
> PutAzureDataLakeStorage. The file is uploaded into a temporary directory
> first and then moved to the final location.
> The motivation behind this was that the file upload with Azure client API is
> a 2-step process: first an empty file is created, then the content is
> uploaded. The unfinished empty file would be available for listing /
> fetching. Also, if the put processor is in 'replace' mode and the uploading
> fails, then old content is lost as the file was already cleared.
> However, this behaviour is not desired in all cases and writing the file
> directly to its final location would be preferred. E.g. when ACL is used for
> permission handling and the temporary folder would need extra administration
> (and the files are not listed/read in parallel so there is no issue with the
> partially written files).
> Add 'Writing Strategy' property with 'Write and Rename' (current behaviour,
> default) and 'Simple Write' options.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
