sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (SLING-7544) Make optimized alias lookup non-blocking
Date Wed, 21 Mar 2018 14:23:00 GMT


ASF GitHub Bot commented on SLING-7544:

DominikSuess commented on a change in pull request #5: SLING-7544 - improving optimized alias
lookup to not block during int…

 File path: src/main/java/org/apache/sling/resourceresolver/impl/mapping/
 @@ -1027,12 +1044,28 @@ private boolean addEntry(final Map<String, List<MapEntry>>
entryMap, final Strin
     private Map<String, Map<String, String>> loadAliases(final ResourceResolver
resolver) {
         final Map<String, Map<String, String>> map = new ConcurrentHashMap<>();
-        final String queryString = "SELECT sling:alias FROM nt:base WHERE sling:alias IS
-        final Iterator<Resource> i = resolver.findResources(queryString, "sql");
-        while (i.hasNext()) {
-            final Resource resource =;
-            loadAlias(resource, map);
-        }
+        String queryString = "SELECT sling:alias FROM nt:base WHERE sling:alias IS NOT NULL";
+		if (this.factory.isForceNoAliasTraversal()) {
+			queryString += " option(traversal fail)";
 Review comment:
   Yes this option was added in - this is the
reason why I made this configurable. Afair (to be confirmed) the query will fail with corresponding
exception if the queryengine doesn't understand the option.

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> Make optimized alias lookup non-blocking
> ----------------------------------------
>                 Key: SLING-7544
>                 URL:
>             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

This message was sent by Atlassian JIRA

View raw message