[OAK-4653] nodetype index can create unusable nodes under index structures

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Component/s: property-index
• Assignee: Vikas Saurabh
• Reporter: Vikas Saurabh
• Created: 07/Aug/16 21:39
• Updated: 08/Oct/19 15:21

Description

nodetype index is just a special property index definition with definition declaring to index jcr:primaryType and jcr:mixinTypes.
Since, it's just property index, we can specify declaringNodeTypes too to filter which type of nodes get indexed.

On query side, declaringNodeTypes are used to check whether the index can be used at all or not.

Now, for nodetype, if node being indexed passes declaringNodeType filter (either primary type or mixin matches), then all its mixins and primaryType gets indexed irrespective of whether declaringNodeType contains it or not.
This is perfectly correct behavior from property index point of view. But, in this regards, we should treat nodetype index to be special and index only those property values that are part of declaring node types.

Issue Links

• is blocked by: OAK-4637 Property index: include/exclude key pattern list
• is cloned by: OAK-6835 nodetype lucene index can create unusable nodes under index structures