[
https://issues.apache.org/jira/browse/OAK-4975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15594911#comment-15594911
]
Marcel Reutegger commented on OAK-4975:
---------------------------------------
In general I also prefer a simple solution. How would a project using Oak
disable a default configuration entry with above approaches?
Other default configuration entries that may be useful:
- rep:NodeType for JCR node types under /jcr:system/jcr:nodeTypes
- rep:VersionStorage for intermediate version storage nodes under /jcr:system.
We would probably have to limit it to one level. Each intermediate version
storage node can have up to 255 child nodes.
- oak:QueryIndexDefinition with one level that includes well known child nodes
like: {{:data}}, {{:status}}, {{indexRules}}, {{:references}},
{{:weakreferences}}. Maybe include even more under {{indexRules}}?
> Setup a default Bundling config
> -------------------------------
>
> Key: OAK-4975
> URL: https://issues.apache.org/jira/browse/OAK-4975
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core, documentmk
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Fix For: 1.6
>
>
> With Bundling Node feature done it would be useful to have a default bundling
> config in Oak. Currently there is a {{BundlingConfigInitializer}} which sets
> up config for {{nt:file}}
> This task is meant to determine
> # What all bundling rules we define by default
> # How this bundling config is setup
> {{BundlingConfigInitializer}} is being used in
> {{OakDocumentMemRepositoryStub}} so gets some coverage in TCK test
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
