[
https://issues.apache.org/activemq/browse/CAMEL-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47700#action_47700
]
Claus Ibsen commented on CAMEL-1099:
------------------------------------
To review:
- I have set the default cache size of the memory to 1000, is this a good
default value?
- FileConsumer code
- file.getName is that a sufficient key for idempotent check (should we use
absolute file name instead?)
- Is the header keys for index/total a good key name?
- Should idempotent be enabled by default?
Notice for unit tests that want to consume files but not delete:
noop=true&idempotent=true will be as before, only consuming the file ones and
not delete the source files.
> File consumer should keep track of processed files
> --------------------------------------------------
>
> Key: CAMEL-1099
> URL: https://issues.apache.org/activemq/browse/CAMEL-1099
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core, camel-ftp, camel-spring
> Reporter: Jonathan Anstey
> Assignee: Jonathan Anstey
> Fix For: 2.0.0
>
>
> See thread:
> http://www.nabble.com/Deprecation-of-file-consumer-timestamp-td20566034s22882.html
> Will be following Gert's suggestion of multiple implementations for the
> storage mechanism so many use cases can be covered:
> - an in-memory store for testing purposes
> - a file-based implementation for basic production environments
> - a database- or ldap-backed implementation for clustered environments, where
> a file can arrive through multiple directories
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
