Drew,

No, you are not crazy. Currently, the FTP/SFTP consumers don't support this. They store the lastPollTimestamp internally and compare that to the file's timestamps to determine if a file still needs to be processed. However, the lastPollTime isn't being persisted anywhere, so restarting the JVM will result in re-reading the files.

If you want, you can always provide a patch for the file-handling strategies you want to use for your project. Let us know if you need any help with that... Any (even partial) solution for this issue would be more than welcome.

If you are using Camel inside ServiceMix, you can also use ServiceMix's FTP poller component as a (temporary) workaround. That one does already support most forms of file-handling (delete, move, ...).


Regards,

Gert



Drew McAuliffe wrote:
Am I crazy or is there no way that the FTP/SFTP consumers do anything to a
source file once they've read it? There doesn't appear to be any delete or
move option like with the File consumer. What possible use case would that
support? Doesn't this pretty much guarantee that an FTP/SFTP consumer will
continuously re-read files, never stopping?

It appears that there's a JIRA issue to add support for something similar to
a file renaming strategy, but it doesn't look like it's slated for anything
in 1.4.

Reply via email to