[jira] [Comment Edited] (CAMEL-20027) camel-file - Read lock changed - Add option for minWaitTime

["Anirudh Prakash (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CAMEL-20027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17942142#comment-17942142 ] 

Anirudh Prakash edited comment on CAMEL-20027 at 4/9/25 9:23 AM:
-----------------------------------------------------------------

[~davsclaus] what should the interaction between minWaitTime and minAge be like? Should the wait time be applied after the minAge or the wait time would be considered from start time?


was (Author: JIRAUSER309186):
[~davsclaus] what should the interaction between minWaitTime and minAge be like? Should the wait time be applied after the minAge?

> camel-file - Read lock changed - Add option for minWaitTime
> -----------------------------------------------------------
>
>                 Key: CAMEL-20027
>                 URL: https://issues.apache.org/jira/browse/CAMEL-20027
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-file
>            Reporter: Claus Ibsen
>            Priority: Minor
>             Fix For: 4.x
>
>
> The changed that causes some problems has been reverted. See CAMEL-20023.
> For users that want the "new broken behaviour" we could have a new option to set a minimum-wait-time.
> This can be needed for users that copy files with preserve old timestamp, and the copy operation is slow and still in progress.
> Then the minimum-wait-time can be used to keep cycling and detecting file changes (size) as the timestamp is preserved and stay constant.



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