[ https://issues.apache.org/jira/browse/OAK-3005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14695600#comment-14695600 ]
Michael Marth commented on OAK-3005: ------------------------------------ [~shgupta], looking at the above configs from a user's perspective I have an issue: IIUC the CachingFDS is configured as basically a "new" DS, i.e. different from the existing FDS. However, I would tend to see the caching aspect as an additional feature of the FDS that can optionally be enabled - hence not creating a (perceived) totally new deployment option, but rather enhancing an existing one. So that would mean that FileDataStore.config would get some new options and we would not have a CachingFDS.config. It maybe reads as if I was just juggling semantics - but I would like to limit the complexity for users WDYT? > OSGI wrapper service for Jackrabbit CachingFDS > ---------------------------------------------- > > Key: OAK-3005 > URL: https://issues.apache.org/jira/browse/OAK-3005 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: blob > Affects Versions: 1.0.15 > Reporter: Shashank Gupta > Assignee: Shashank Gupta > Labels: candidate_oak_1_0, candidate_oak_1_2, docs-impacting, > features, performance > Fix For: 1.3.1 > > Attachments: OAK-2729.patch, > org.apache.jackrabbit.oak.plugins.blob.datastore.CachingFDS.sample.config > > > OSGI service wrapper for JCR-3869 which provides CachingDataStore > capabilities for SAN & NAS storage -- This message was sent by Atlassian JIRA (v6.3.4#6332)