[
https://issues.apache.org/jira/browse/CAMEL-26060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18130918#comment-18130918
]
Claus Ibsen commented on CAMEL-26060:
-------------------------------------
Yeah you are welcome to send a PR
> camel-file-watch - CamelFileLastModified is the time of the event, not of the
> file
> ----------------------------------------------------------------------------------
>
> Key: CAMEL-26060
> URL: https://issues.apache.org/jira/browse/CAMEL-26060
> Project: Camel
> Issue Type: Bug
> Components: camel-file-watch
> Affects Versions: 4.18.0, 4.22.0, 4.23.0
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: 4.24.0
>
>
> Found while adding the catalog body types of file-watch (CAMEL-24961),
> checked with {{camel run}}.
> h4. 1. CamelFileLastModified is the time of the event
> The header is set to the date of the event ({{FileWatchConsumer}}, main
> 5aac7df76b83, line 174), but its doc says "A Long value containing the last
> modified timestamp of the file." ({{FileWatchConstants}}, line 57). Checked
> on 4.24.0-SNAPSHOT with {{camel run}}: a file with the modified time
> 2020-01-01 changed gave the time of the change in the header.
> *Proposed change*: set the last modified time of the file, or say in the doc
> that it is the time of the event.
> h4. Also read in the code, not run
> * When the queue (queueSize) is full, an event is dropped without a log
> ({{eventQueue.offer}}, line 224).
> _Claude Code on behalf of davsclaus_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
