You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2022/09/02 09:06:00 UTC
[jira] [Updated] (CAMEL-9324) camel-file - Changed read-lock to keep state between polls to allow to be faster
[ https://issues.apache.org/jira/browse/CAMEL-9324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-9324:
-------------------------------
Summary: camel-file - Changed read-lock to keep state between polls to allow to be faster (was: Changed read-lock to keep state between polls to allow to be faster)
> camel-file - Changed read-lock to keep state between polls to allow to be faster
> --------------------------------------------------------------------------------
>
> Key: CAMEL-9324
> URL: https://issues.apache.org/jira/browse/CAMEL-9324
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, camel-ftp
> Reporter: Claus Ibsen
> Priority: Major
> Fix For: Future
>
>
> See nabble
> http://camel.465427.n5.nabble.com/sftp-endpoint-is-not-as-performant-as-expected-tp5773654p5773879.html
> Yeah the current changed read-lock afair don't keep state between
> polls. So we could look into one that does that, and do a full scan of
> all the files, and then do a change detect on all files all together
> and make up which ones hasn't changed. And that way can react faster
> than currently.
> Now that may require doing more file directory listings to gather all
> those files and their timestamps / size to see which one has changed,
> instead of monitoring a single file one by one. Also it may mean that
> files can be processed out of order, if a file sort isn't must be
> strictly followed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)