[
https://issues.apache.org/jira/browse/CAMEL-27060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-27060.
---------------------------------
Resolution: Fixed
> camel-file, camel-ftp, camel-smb - idempotentRepository and idempotentKey are
> ignored without idempotent=true, and nothing says so
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-27060
> URL: https://issues.apache.org/jira/browse/CAMEL-27060
> Project: Camel
> Issue Type: Bug
> Components: camel-file, camel-ftp, camel-smb
> Reporter: Federico Mariani
> Assignee: Federico Mariani
> Priority: Minor
> Fix For: 4.24.0
>
>
> The file, ftp, ftps, sftp and smb consumers use the {{idempotentRepository}}
> and {{idempotentKey}} options only with {{idempotent=true}} ({{noop=true}}
> turns it on). Set alone, they do nothing: the consumer does not look in the
> repository and does not skip the files already consumed. Several consumers
> that poll the same directory with a shared repository consume the same file
> more than once. Nothing is logged.
> {code:java}
> from("file:inbox?idempotentRepository=#myRepo&idempotentKey=${file:name}")
> .to("mock:result"); // receives inbox/a.txt, although a.txt is in myRepo
> {code}
> Expected: a WARN when the consumer is created, that names
> {{idempotent=true}}, and option descriptions that say when the options apply.
> The idempotent read locks of the file component ({{readLock=idempotent}},
> {{idempotent-changed}}, {{idempotent-rename}}) use these options without
> {{idempotent=true}}: no WARN there.
> _Claude Code on behalf of Federico Mariani_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)