[jira] [Updated] (NIFI-12928) Add Simple Write strategy in PutAzureDataLakeStorage
[ https://issues.apache.org/jira/browse/NIFI-12928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Villard updated NIFI-12928: -- Fix Version/s: 1.26.0 > 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, 1.26.0 > > Time Spent: 1h 40m > 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)
[jira] [Updated] (NIFI-12928) Add Simple Write strategy in PutAzureDataLakeStorage
[ https://issues.apache.org/jira/browse/NIFI-12928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Villard updated NIFI-12928: -- Fix Version/s: 2.0.0-M3 Resolution: Fixed Status: Resolved (was: Patch Available) > 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: 1h 20m > 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)
[jira] [Updated] (NIFI-12928) Add Simple Write strategy in PutAzureDataLakeStorage
[ https://issues.apache.org/jira/browse/NIFI-12928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Turcsanyi updated NIFI-12928: --- Status: Patch Available (was: Open) > 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 > Time Spent: 10m > 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)
