jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chetan Mehrotra (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (OAK-2300) QueryEngine should also make use of jcr:primaryType property restriction for NodeType condition
Date Thu, 30 Jul 2015 04:21:04 GMT

     [ https://issues.apache.org/jira/browse/OAK-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chetan Mehrotra resolved OAK-2300.
----------------------------------
       Resolution: Duplicate
    Fix Version/s:     (was: 1.3.4)

> QueryEngine should also make use of jcr:primaryType property restriction for NodeType
condition
> -----------------------------------------------------------------------------------------------
>
>                 Key: OAK-2300
>                 URL: https://issues.apache.org/jira/browse/OAK-2300
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: query
>            Reporter: Chetan Mehrotra
>            Priority: Minor
>
> Queries generated by Jackrabbit GQL support [1] specifies nodeType as property restrictions
> {noformat}
> SELECT [jcr:path],
>        [jcr:score],
>        *
> FROM   [nt:base] AS a
> WHERE  Isdescendantnode(a, '/content/dam')
> AND    CONTAINS([jcr:content/metadata/dc:format], 'image')
> AND    [jcr:primarytype] = 'dam:Asset'
> AND    CONTAINS(*, 'foo')
> {noformat}
> For above query the {{Filter.matchesAllTypes}} returns true which is not the intention.
This causes issues with {{LucenePropertyIndex}} as it determines the applicable {{indexingRule}}
based on the nodeType.
> It would be helpful if QueryEngine takes into account such propertyRestrictions or we
fix GQL!
> [1] http://jackrabbit.apache.org/api/2.1/org/apache/jackrabbit/commons/query/GQL.html



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

Mime
View raw message