You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Peter Turcsanyi (Jira)" <ji...@apache.org> on 2023/06/26 21:07:00 UTC

[jira] [Updated] (NIFI-11758) Add local file upload option in PutAzure*Storage processors

     [ https://issues.apache.org/jira/browse/NIFI-11758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Turcsanyi updated NIFI-11758:
-----------------------------------
    Description: 
There are cases when the files to be uploaded to Azure Storage are available on the local filesystem where NiFi is running. That is, the flow could read and upload the files directly from the filesystem without adding it in NiFi's content repo which is an overhead in this case (can be relevant for huge files).

Add "Data to Upload" property with options "FlowFile's Content" (default, current behaviour) and "Local File". Using the latter, the user can by-pass the content repo and upload the file from the local filesystem to Azure Storage directly.

  was:
There are cases when the files to be uploaded to Azure Storage are available on the local filesystem where NiFi is running. That is, the flow could read and upload the file directly from the filesystem without adding it in NiFi's content repo which is an overhead in this case (can be relevant for huge files).

Add "Data to Upload" property with options "FlowFile's Content" (default, current behaviour) and "Local File". Using the latter, the user can by-pass the content repo and upload the file from the local filesystem to Azure Storage.


> Add local file upload option in PutAzure*Storage processors
> -----------------------------------------------------------
>
>                 Key: NIFI-11758
>                 URL: https://issues.apache.org/jira/browse/NIFI-11758
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Peter Turcsanyi
>            Assignee: Peter Turcsanyi
>            Priority: Major
>
> There are cases when the files to be uploaded to Azure Storage are available on the local filesystem where NiFi is running. That is, the flow could read and upload the files directly from the filesystem without adding it in NiFi's content repo which is an overhead in this case (can be relevant for huge files).
> Add "Data to Upload" property with options "FlowFile's Content" (default, current behaviour) and "Local File". Using the latter, the user can by-pass the content repo and upload the file from the local filesystem to Azure Storage directly.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)