[
https://issues.apache.org/jira/browse/CAMEL-12990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16718991#comment-16718991
]
Claus Ibsen commented on CAMEL-12990:
-------------------------------------
Even if you use localWorkDirectory and without stream download, and do a
from -> to
Then Camel is optimized to move the file (if possible) via a file rename
operation, and only fallback to a copy/delete if not possible. That ought to be
a fast operation even for big files. So this feature should be there out of the
box.
> FTP endpoint with 'localWorkDirectory' considers File Consumer's 'noop' option
> ------------------------------------------------------------------------------
>
> Key: CAMEL-12990
> URL: https://issues.apache.org/jira/browse/CAMEL-12990
> Project: Camel
> Issue Type: New Feature
> Components: camel-ftp
> Affects Versions: 2.22.1
> Reporter: Gerold Broser
> Priority: Minor
> Labels: feature, ftp
> Fix For: 2.24.0
>
>
> [https://camel.apache.org/ftp2.html] reads:
> {quote}See [File|https://camel.apache.org/file2.html] for more options as all
> the options from [File|https://camel.apache.org/file2.html] is inherited.
> {quote}
> and in *Using Local Work Directory*:
> {quote}And finally, when the Exchange is complete the local file is deleted.
> {quote}
> [https://camel.apache.org/file2.html] reads:
> {quote}
> |{{noop}}|{{false}}|If *{{true}}*, the file is not moved or deleted in any
> way.|
> {quote}
> I have a use case where I'd need the file transferred to
> \{{localWorkDirectory}} to stay there. Otherwise I have to change
> \{{localWorkDirectory}} to something else and add a Producer endpoint to my
> route which copies the file to the intended directory (i.e. the former
> \{{localWorkDirectory}}), which is inconvenient with GiB-size files.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
