jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-1744) GQL queries with "jcr:primaryType='x'" don't use the node type index
Date Fri, 29 Jan 2016 07:34:39 GMT

    [ https://issues.apache.org/jira/browse/OAK-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15123140#comment-15123140
] 

Thomas Mueller commented on OAK-1744:
-------------------------------------

> it means nodetype should have exact match

Yes, that's why I left "and [jcr:primaryType] = 'asset'" in the subquery. So the subquery
has both "from [asset]" and the "[jcr:primaryType] = 'asset'" condition, so I guess it should
work well.

So, I will propose a patch after I have tested it.

> GQL queries with "jcr:primaryType='x'" don't use the node type index
> --------------------------------------------------------------------
>
>                 Key: OAK-1744
>                 URL: https://issues.apache.org/jira/browse/OAK-1744
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: query
>            Reporter: Thomas Mueller
>            Assignee: Thomas Mueller
>            Priority: Minor
>             Fix For: 1.3.15
>
>
> GQL queries (org.apache.jackrabbit.commons.query.GQL) with type restrictions are converted
to the XPath condition "jcr:primaryType = 'x'". This conditions is not currently interpreted
as a regular node type restriction in the query engine or the node type index, as one would
expect. 
> Such restrictions could still be processed efficiently using the property index on "jcr:primaryType",
but if that one is disabled (by setting the cost manually very high, as it is done now), then
such queries don't use the expected index.
> I'm not sure yet where this should be best fixed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message