[
https://issues.apache.org/jira/browse/CAMEL-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-2934.
--------------------------------
Resolution: Fixed
Fix Version/s: (was: Future)
2.8.0
Thanks for the patch. I had to do a few adjustments to keep the current
behavior for the other read lock options.
We may want to improve and look into if its possible to gather file
modification / file size details without doing a list dir operation.
I set the default interval to 5 sec and timeout for 20 sec for FTP. For files
its 1 sec and 10 sec.
> Port the changed readLock to be avail for camel-ftp as well
> -----------------------------------------------------------
>
> Key: CAMEL-2934
> URL: https://issues.apache.org/jira/browse/CAMEL-2934
> Project: Camel
> Issue Type: New Feature
> Components: camel-ftp
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.8.0
>
> Attachments: FtpChangedLockStrategy.java,
> FtpProcessStrategyFactory.java, SftpChangedLockStrategy.java,
> SftpProcessStrategyFactory.java, ftp, ftps, sftp
>
>
> The {{changed}} read lock
> http://camel.apache.org/file2.html
> Is currently only avail for the file component. We should make it generic to
> leverage the operations API so we can use it from FTP also.
> And we should allow URI parameters to configure it using {{readLock.}}
> prefix, so you can do
> {{readLock.timeout=5000&readLock.changedInterval=2000}}
> This means the {{readLockTimeout}} should be @deprecated as we just leverage
> the Camel prefix properties mechanism to auto set the options.
> The {{changed}} read lock should also have a new option to set the _steady_
> interval. The time period in which the file must *not* have been changed.
> Currently its fixed to 1 second. But end users could set it to 5 sec. to
> ensure that the file hasn't been touched for that min. period.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
