[jira] [Resolved] (CAMEL-19378) File Changed ReadLock Strategy with minAge only looks for lastModified

["Claus Ibsen (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-19378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-19378.
---------------------------------
    Fix Version/s: 3.18.8
                   3.20.6
         Assignee: Claus Ibsen
       Resolution: Fixed

> File Changed ReadLock Strategy with minAge only looks for lastModified
> ----------------------------------------------------------------------
>
>                 Key: CAMEL-19378
>                 URL: https://issues.apache.org/jira/browse/CAMEL-19378
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-file
>            Reporter: David Voit
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 3.18.8, 3.20.6, 3.21.0, 4.0-RC1, 4.0
>
>
> If a file is copied with the original lastModified date, files are processes instantly. Also the file change detection is disabled if a copy takes more than minAge time. Instead of comparing startTime with lastModified on each iteration we are comparing it with now(). If files are created anew this should be the same behaviour, and files copied with preserved lastModifed are still correctly checked.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)