[
https://issues.apache.org/jira/browse/CAMEL-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972414#action_12972414
]
Claus Ibsen commented on CAMEL-3163:
------------------------------------
This is a bit more tricky as we have to support two kinds
a) 1 done file per real file
b) 1 done file per directory
Supporting (a) is more simple because its easy to correlate to the real file.
Supporting (b) is more tricky as what should be the rules when the done file is
safe to be deleted?
That all the files in the directory has been processed? Such as the directory
being empty?
For starters I think we will go with (a) and then consider if (b) is used out
in the real life? I do have a vague idea that it is.
> Add look for mark file feature to file consumer
> -----------------------------------------------
>
> Key: CAMEL-3163
> URL: https://issues.apache.org/jira/browse/CAMEL-3163
> Project: Camel
> Issue Type: New Feature
> Components: camel-core, camel-ftp
> Affects Versions: 2.4.0
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: 2.6.0
>
>
> Its still common to transfer data using files and using a marker file when
> the data is ready.
> We should have a feature on the file consumer, so it can be used to scan for
> marker files, and then use the real file as the message body.
> And then when its done it can delete/move both files.
> The problem is how to define an easy way of correlating the marker file to
> the real file. We can use an Expression for that.
> For example maybe something like, (use better option names)
> {{realFile=${file:name.noext}.csv&include=.*.ready}}
> Then Camel will react when there is a .ready file in the folder. And evaluate
> the expression and see if a file with that result exists.
> When it's done the marker file should be deleted, and the real file should be
> moved using the existing options for that.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
