[jira] [Resolved] (SLING-4951) Make query for validation models more Oak-friendly

["Konrad Windszus (JIRA)" <ji...@apache.org>]

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

Konrad Windszus resolved SLING-4951.
------------------------------------
    Resolution: Fixed

Fixed with r1696271 by removing the path constraint for a parent resource named {{validation}}. The index for the property {{validatedResourceType}} is still necessary though (but can be easily added via oak:QueryIndexDefinition nodes, see http://jackrabbit.apache.org/oak/docs/query/query.html).

> Make query for validation models more Oak-friendly
> --------------------------------------------------
>
>                 Key: SLING-4951
>                 URL: https://issues.apache.org/jira/browse/SLING-4951
>             Project: Sling
>          Issue Type: Improvement
>          Components: Validation
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>             Fix For: Validation 1.0.0
>
>
> Currently the {{ResourceValidationModelProviderImpl}} is looking for appropriate models with the following query:
> {{/jcr:root/apps//validation//*[@sling:resourceType="sling/validation/model" and @validatedResourceType="<some resource type>"}}
> This leads to warnings like this in OAK:
> {code}
> 14.08.2015 14:07:04.659 *WARN* [0:0:0:0:0:0:0:1 [1439554021017] GET <some path> HTTP/1.1] org.apache.jackrabbit.oak.spi.query.Cursors$TraversingCursor Traversed 8000 nodes with filter Filter(query=select b.[jcr:path] as [jcr:path], b.[jcr:score] as [jcr:score], b.* from [nt:base] as a inner join [nt:base] as b on isdescendantnode(b, a) where name(a) = 'validation' and isdescendantnode(a, '/apps') and b.[sling:resourceType] = 'sling/validation/model' and b.[validatedResourceType] = '<some resource type>' /* xpath: /jcr:root/apps//validation//*[@sling:resourceType="sling/validation/model" and @validatedResourceType="<some resource type>"] */, path=/apps//*); consider creating an index or changing the query
> {code}



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