You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Malthe Borch (Jira)" <ji...@apache.org> on 2022/10/03 12:46:00 UTC
[jira] [Updated] (NIFI-10491) Azure Blob Storage should have conflict resolution (overwrite mode)
[ https://issues.apache.org/jira/browse/NIFI-10491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Malthe Borch updated NIFI-10491:
--------------------------------
Description:
PutAzureBlobStorage_v12 currently does not have configurable conflict resolution.
If a blob already exists, the flow file is lead to the failure relationship.
Instead, there should be three options for conflict behavior:
# Fail
# Replace
# Ignore
This is similar to PutAzureDataLakeStorage.
was:
PutAzureBlobStorage_v12 currently does not have configurable conflict resolution.
If a blob already exists, the flow file is lead to the failure relationship.
Instead, there should be three options for conflict behavior:
# Fail
# Replace
# Ignore
This is similar to PutDataLakeStorage.
> Azure Blob Storage should have conflict resolution (overwrite mode)
> -------------------------------------------------------------------
>
> Key: NIFI-10491
> URL: https://issues.apache.org/jira/browse/NIFI-10491
> Project: Apache NiFi
> Issue Type: New Feature
> Reporter: Malthe Borch
> Assignee: Malthe Borch
> Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> PutAzureBlobStorage_v12 currently does not have configurable conflict resolution.
> If a blob already exists, the flow file is lead to the failure relationship.
> Instead, there should be three options for conflict behavior:
> # Fail
> # Replace
> # Ignore
> This is similar to PutAzureDataLakeStorage.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)