[
https://issues.apache.org/jira/browse/OAK-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13761649#comment-13761649
]
Thomas Mueller commented on OAK-985:
------------------------------------
> I think it should add the jcr:primaryType condition to the node type
> conditions
I'm not completely sure what is the best approach. Usually, restricting the
node type is hierarchy-aware, so that "nt:file" means "nt:file and all children
of nt:file", whereas "jcr:primaryType = 'nt:file'" means "really just nt:file".
> the query engine will not be able to pick up the node type index
Isn't the node type index based on a property index on jcr:primaryType, and
this property index is also visible to the query engine? If yes, shouldn't the
query engine use this property index instead of traversal?
> The query engine doesn't properly extract the node type information from
> queries with conditions on jcr:primaryType
> -------------------------------------------------------------------------------------------------------------------
>
> Key: OAK-985
> URL: https://issues.apache.org/jira/browse/OAK-985
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core, query
> Reporter: Alex Parvulescu
>
> Given the following query:
> {code}
> //*[(jcr:contains(., 'dog')) and @jcr:primaryType = 'nt:file']
> {code}
> The query engine will generate a filter with a match-all clause on the node
> type and a property restriction on _jcr:primaryType_ to the value 'nt:file'.
> I think it should add the _jcr:primaryType_ condition to the node type
> conditions, and not to the node property ones.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
