[
https://issues.apache.org/jira/browse/OAK-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844353#comment-13844353
]
Thomas Mueller commented on OAK-1150:
-------------------------------------
> The node type index is configurable via a white list
Yes, that's true. I first thought it makes sense to add a feature to create a
blacklist, but a whitelist actually is better.
> Does the default setup, JCR's include all node types policy, need any changes?
I think it would make sense to restrict the default Oak nodetype index to the
following list:
{code}
"sling:MessageEntry", "sling:VanityPath", "sling:chunks", "slingevent:Job",
"slingevent:TimedEvent"
{code}
I think the node types "rep:Authorizable", "rep:User", and "rep:Group" don't
need to be indexed, but I might be wrong.
> NodeType index: don't index all primary and mixin types
> -------------------------------------------------------
>
> Key: OAK-1150
> URL: https://issues.apache.org/jira/browse/OAK-1150
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core
> Reporter: Thomas Mueller
> Fix For: 0.14
>
>
> Currently, the nodetype index indexes all primary types and mixin types
> (including nt:base I think).
> This results in many nodes in this index, which unnecessarily increases the
> repository size, but doesn't really help executing queries (running a query
> to get all nt:base nodes doesn't benefit much from using the nodetype index).
> It should also help reduce writes in updating the index, for example for
> OAK-1099
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
