[
https://issues.apache.org/jira/browse/NIFI-9972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783753#comment-17783753
]
ASF subversion and git services commented on NIFI-9972:
-------------------------------------------------------
Commit 0fe9d2b56fc7023843edc6a95ab95e735179d4de in nifi's branch
refs/heads/main from Malthe Borch
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=0fe9d2b56f ]
NIFI-9972 Added CopyAzureBlobStorage_v12 Processor
This closes #6941
Signed-off-by: David Handermann <[email protected]>
> Azure Blob Storage "Blob from URL"
> ----------------------------------
>
> Key: NIFI-9972
> URL: https://issues.apache.org/jira/browse/NIFI-9972
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Malthe Borch
> Assignee: Malthe Borch
> Priority: Major
> Time Spent: 7h
> Remaining Estimate: 0h
>
> The Azure SDK for Azure Blob Storage supports the "Put Blob from URL" and
> "Copy from URL" operations which allow server-to-server copying of blobs from
> one storage account to another.
> This is perhaps antithetical to data processing in NiFi (since the
> implication is that the client does not actually see any of the data being
> transferred), but it is a very relevant data operation.
> Today, to accomplish the same from NiFi you would need to call out to for
> example
> [azcopy|https://docs.microsoft.com/en-us/azure/storage/common/storage-ref-azcopy]
> which means you lose out on credentials management etc.
> Practically speaking, you would provide two credentials, one for the source
> and another for the destination and the would-be processor would then engage
> in the server-to-server copying operation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
