sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dominik Süß (JIRA) <j...@apache.org>
Subject [jira] [Commented] (SLING-7544) Make optimized alias lookup non-blocking
Date Mon, 19 Mar 2018 16:15:00 GMT

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

Dominik Süß commented on SLING-7544:
------------------------------------

Fixed patch to properly handle traversal, fixed mistake on cleanup accidentially moving thread
out of optimized if condition & added test coverage for the delayed cases.

> Make optimized alias lookup non-blocking
> ----------------------------------------
>
>                 Key: SLING-7544
>                 URL: https://issues.apache.org/jira/browse/SLING-7544
>             Project: Sling
>          Issue Type: Improvement
>          Components: ResourceResolver
>    Affects Versions: Resource Resolver 1.5.36
>            Reporter: Dominik Süß
>            Priority: Major
>
> The implementation of optimized alias lookup as introduced with SLING-2521 blocks CommonResourceResolver activation
while loading aliases to fillup the aliasmap. In case a corresponding index is not present
yet this can lead to full tree traversal while indexing is doing the same in the background.
> The proposed improvements are:
> * making loading of the aliasmap happen asynchronously
> * only use optimized handling as soon as aliasmap is built
> * wait for non traversal index (optional - forced by default, can be turned off for small
datasets)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message