[
https://issues.apache.org/jira/browse/CAMEL-12041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16275943#comment-16275943
]
ASF GitHub Bot commented on CAMEL-12041:
----------------------------------------
drekbour opened a new pull request #2127: CAMEL-12041 Introduce
ConcurrentMapIdempotentRepository and MapIdempotentRepository
URL: https://github.com/apache/camel/pull/2127
+ Introduce AbstractIdempotentRepositoryTest
Rebased, tested and checkstyle'd.
The new tests duplicate and obselete a great number of the existing
Idempotent* and FileIdempotent* tests but I have NOT deleted the pre-existing
ones. I can update this PR with those deletions if requested.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Introduce ConcurrentMapIdempotentRepository and MapIdempotentRepository
> -----------------------------------------------------------------------
>
> Key: CAMEL-12041
> URL: https://issues.apache.org/jira/browse/CAMEL-12041
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 2.20.1
> Reporter: Marc Carter
> Priority: Trivial
>
> In order to more generically plug in third-party data fabrics, Camel should
> directly support the ConcurrentMap interface.
> 1 Add an explicit ConcurrentMapIdempotentRepository (which does away with
> synchronized blocks around the backing map)
> 2 Factor our MapIdempotentRepository from MemoryIdempotentRepository (being
> based on a Map _interface_ doesn't make it "memory" - only the default
> LRUCache impls are definitively "memory")
> 3 Make some sense of the tests around this EIP
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)