[ 
https://issues.apache.org/jira/browse/NIFI-16159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18109564#comment-18109564
 ] 

ASF subversion and git services commented on NIFI-16159:
--------------------------------------------------------

Commit 5c9093a9845329a5886289e8620953dbcc2d43a9 in nifi's branch 
refs/heads/main from Shubham Sharma
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=5c9093a9845 ]

NIFI-16159 Add support for FileResourceService in PutFile (#11495)

Signed-off-by: David Handermann <[email protected]>

> Add support for FileResourceService in PutFile
> ----------------------------------------------
>
>                 Key: NIFI-16159
>                 URL: https://issues.apache.org/jira/browse/NIFI-16159
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Shubham Sharma
>            Priority: Minor
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> {{PutS3Object}} (NIFI-12642), {{PutGCSObject}} (NIFI-12643), and {{PutHDFS}} 
> (NIFI-12801) already let users pick the transfer source — either the incoming 
> FlowFile's content or a local file resolved through a {{FileResourceService}} 
> — via the standard {{Resource Transfer Source}} / {{File Resource Service}} 
> properties.
> {{PutFile}} still writes only the FlowFile content. Users who want to stage a 
> local file to a directory on disk have to first pull it into a FlowFile with 
> {{FetchFile}} / {{{}GetFile{}}}, which is wasteful when the source is already 
> a path on the local filesystem (or reachable via a custom 
> {{FileResourceService}} implementation).
> This ticket adds the same two properties to {{PutFile}} so it can:
>  * read from the incoming FlowFile content (existing default behavior — 
> unchanged), or
>  * read from a {{FileResourceService}} (new), streaming the resource straight 
> to the destination directory.



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

Reply via email to