[
https://issues.apache.org/jira/browse/SLING-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17440443#comment-17440443
]
Henry Kuijpers commented on SLING-2783:
---------------------------------------
[~cziegeler], while profiling our application, we notice that for all servlets
we have registered (roughly 2800) an entry is made in the `excludedPaths`
"PathSet". It means that for every result that comes back from the query, that
check is executed and there are 2800 iterations per result. Our resultset is
1800 resources, which means we're doing 1800x2800=alot iterations. We see quite
an impact in the performance.
Was this intended? Or was the assumption, back in the day, that there were a
handful of those entries in the "excludedPaths"-field?
> Search implementation does not respect resource providers
> ---------------------------------------------------------
>
> Key: SLING-2783
> URL: https://issues.apache.org/jira/browse/SLING-2783
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Affects Versions: JCR Resource 2.2.4
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Priority: Major
> Fix For: JCR Resource 2.7.0
>
>
> If a search is performed by the JCR Resource Provider the returned set is not
> checked whether these resources/nodes are accessible through the resource
> tree.
> For example a different resource provider might be mounted at /libs -
> therefore all results for this sub tree need to be discarded.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
