[
https://issues.apache.org/jira/browse/SLING-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-5084.
-----------------------------------
Resolution: Fixed
Completed: At revision: 1706299
i applied a subset of indexes as defined in {{org.apache.sling.jcr.oak.server}}
bundle.
once {{org.apache.sling.jcr.oak.server}} is released we could think about using
this for initializing the repository instead of using
{{org.apache.jackrabbit.oak.jcr.Jcr}} with those extra indexes to be more close
to real oak-jcr setup used by oak-server.
> sling-mock-oak: Provide a minimal index configuration for Sling-related
> properties
> ----------------------------------------------------------------------------------
>
> Key: SLING-5084
> URL: https://issues.apache.org/jira/browse/SLING-5084
> Project: Sling
> Issue Type: Improvement
> Components: Testing
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Priority: Minor
> Labels: mocks
> Fix For: Testing Sling Mock Oak 1.0.0
>
>
> by default, no sling-specific indexes are defined in the JCR_OAK resource
> resolver type for sling mocks. this leads to warnings on every usage (when
> the resource-jcr mapping is initialized) like:
> {noformat}
> WARN org.apache.jackrabbit.oak.spi.query.Cursors$TraversingCursor - Traversed
> 1000 nodes with filter Filter(query=SELECT sling:alias FROM nt:base WHERE
> sling:alias IS NOT NULL, path=*, property=[sling:alias=[is not null]]);
> consider creating an index or changing the query
> {noformat}
> we should provide a minimal index configuration for the default sling
> attribute to avoid these.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
