[
https://issues.apache.org/jira/browse/OAK-11791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18004678#comment-18004678
]
Julian Reschke commented on OAK-11791:
--------------------------------------
The goal should be to only use vendor independant APIs (javax.cache,
hopefully), or on our own.
If we switch to - let's say - Caffeine, we should wrap the API into something
we can support should we ever need to switch impls.
> Gradually replace Guava Cache by javax.cache interfaces
> -------------------------------------------------------
>
> Key: OAK-11791
> URL: https://issues.apache.org/jira/browse/OAK-11791
> Project: Jackrabbit Oak
> Issue Type: Task
> Reporter: Julian Reschke
> Priority: Major
>
> 1. CacheLIRS implements the Guava caching interfaces, but does not use any
> Guava implementation code.
> 2. We could move CacheLIRS code into an internal class, and let CacheLIRS
> still use Guava cache interfaces.
> 3. Then implement a new class based on javax.cache interfaces
> 4. Gradually migrate uses of the Guava Cache interfaces to the javax.cache
> interfaces and the new implementation
> 5. When done, remove old code
> For existing APIs, the main differences appear to be thrown Exceptions and
> return values (boolean vs values)
> The main issue seems to be the complicated way to obtain statistics, and the
> fact the way we expose cache stats in the DocumentNodeStoreService.
> [~thomasm] - what do you think?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
