Re: Nodetype index

Hi, Right now, there is only one nodetype index. So, if you add a nodetype / mixin to that index (as you know the lists of nodetypes / mixins is a multi-valued property), then you need to reindex that index. Which needs to read all the nodes. The alternative would be to have multiple nodetype

Nodetype index

Hey all, Some time ago I asked about creating an oak index based on the node type (primary type or mixin type), after which I was pointed to the nodetype index. I have to say though that there is a serious drawback to this index: I have two separate projects, both having some code based on a

Re: disabling nodetype index

Is it safe to disable nodetype index? We do not have any custom queries that needed it. Is it used for any oak internals? Assuming it is safe to disable, can I follow that by deleting every node under /oak:index/nodetype/:index ? db.nodes.remove({_id: /^\d+:\/oak:ind

disabling nodetype index

Hi all Is it safe to disable nodetype index? We do not have any custom queries that needed it. Is it used for any oak internals? Assuming it is safe to disable, can I follow that by deleting every node under /oak:index/nodetype/:index ? db.nodes.remove({_id: /^\d+:\/oak:index\/nodetype\/:index

Re: NodeType index returns cost as zero when count is zero

:score], * from [nt:unstructured] as a where > [sling:resourceType] = 'dam/smartcollection' and isdescendantnode(a, > '/content/dam') > > where index does exist for sling:resourceType the explain shows that > its using the NodeType index for jcr:primaryType > >

NodeType index returns cost as zero when count is zero

Hi, While trying to execute a query like select [jcr:path], [jcr:score], * from [nt:unstructured] as a where [sling:resourceType] = 'dam/smartcollection' and isdescendantnode(a, '/content/dam') where index does exist for sling:resourceType the explain shows that its using th