[GitHub] [camel] davidvoit commented on pull request #10131: File Changed ReadLock Strategy with minAge only looks for lastModified

davidvoit commented on PR #10131: URL: https://github.com/apache/camel/pull/10131#issuecomment-1553409837 Sure. I will be back in the office on monday and then will modify the patch and create a jira issue. Claus Ibsen ***@***.***> schrieb am Do., 18. Mai 2023, 19:46: > I won

[GitHub] [camel] davidvoit commented on pull request #10131: File Changed ReadLock Strategy with minAge only looks for lastModified

davidvoit commented on PR #10131: URL: https://github.com/apache/camel/pull/10131#issuecomment-1551632497 The use case that a file needs to be in the folder for n seconds (to avoid slow transfers which would not be noticed by the change lock) could also be achieved with increasing the i

[GitHub] [camel] davidvoit commented on pull request #10131: File Changed ReadLock Strategy with minAge only looks for lastModified

davidvoit commented on PR #10131: URL: https://github.com/apache/camel/pull/10131#issuecomment-1551512120 Yeah but this ist not only a Windows thing. A "cp -p" could also lead to broken files on unix systems as the length comparision is skipped and files are instantly triggered C

[GitHub] [camel] davidvoit commented on pull request #10131: File Changed ReadLock Strategy with minAge only looks for lastModified

davidvoit commented on PR #10131: URL: https://github.com/apache/camel/pull/10131#issuecomment-1551320364 I know the patch is not optimal, it's a first draft to more cleary show the changes. Let's see this first draft as an RFC. In the end we don't need to differentiate between minage !=