You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Carsten Ziegeler (Jira)" <ji...@apache.org> on 2022/07/07 04:52:00 UTC

[jira] [Resolved] (SLING-7544) Make optimized alias lookup non-blocking

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

Carsten Ziegeler resolved SLING-7544.
-------------------------------------
    Resolution: Won't Fix

There have  been many changes in this area recently, which I beliebe make this issue obsolete. If there is still an open item, please reopen a new issue 

> 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
>          Time Spent: 4h 20m
>  Remaining Estimate: 0h
>
> 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
(v8.20.10#820010)