[
https://issues.apache.org/jira/browse/OAK-6917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16245560#comment-16245560
]
Marcel Reutegger commented on OAK-6917:
---------------------------------------
Nope, that doesn't work:
{noformat}
org.apache.jackrabbit.oak-store-document bundle
org.apache.jackrabbit.oak-store-document:1.8.0.SNAPSHOT
(107)[org.apache.jackrabbit.oak.plugins.document.DocumentNodeStoreService(213)]
: Field preset in class class
org.apache.jackrabbit.oak.plugins.document.DocumentNodeStoreService has
unsupported type org.apache.jackrabbit.oak.plugins.document.Configuration
{noformat}
Going through the indirection of another service with an optional configuration
works though.
> Configuration presets for DocumentNodeStoreService
> --------------------------------------------------
>
> Key: OAK-6917
> URL: https://issues.apache.org/jira/browse/OAK-6917
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: documentmk
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Priority: Minor
> Fix For: 1.8
>
> Attachments: OAK-6917-alternative-approach.patch, OAK-6917.patch
>
>
> When Oak is deployed in an OSGi container, applications usually want to ship
> a default configuration which is different from the defaults present in Oak.
> E.g. an application may want to use a default cache size of 1G for the
> DocumentNodeStoreService instead of the default 256M. Now if a user of the
> application provides a custom configuration and does not specify the cache
> size, the value for this configuration will flip back to the Oak default of
> 256M.
> There should be a way to configure presets for the application that are
> different from the Oak defaults and then allow a user to customize the
> configuration while still respecting the presets.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
