[SLING-9535] Improve performance of sling:alias Query when Optimize alias resolution is activated

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Resource Resolver 1.7.2
• Component/s: ResourceResolver
• Labels: Sling-12-ReleaseNotes
• Assignee: Robert Munteanu
• Reporter: Leonardo Derks
• Created: 19/Jun/20 16:46
• Updated: 25/Feb/21 18:45
• Resolved: 12/Jan/21 09:34

Description

Improve performance of sling:alias Query when Optimize alias resolution is activated in the Resource Resolver Factory:

By checking the logs at startup this query is executed:

(query=SELECT sling:alias FROM nt:base WHERE sling:alias IS NOT NULL, path=*, property=[sling:alias=[is not null]])

The part that will be good to improve is that the query is not executed for path=, instead a predefined set of locations is used.*

(Something similar as it is for the Vanity Paths will be nice):

Then if none fo these are configured then the query is executed with path=*.

 

In our project several versions are created per page and it turns out that the sling:alias found under /jcr:system/jcr:versionStorage are also including in the query exceeding the 10000 limit mentioned in the warning message of the property:

This might have an impact on the startup time and on the alias update time if the number of aliases is huge (over 10000)

 

We might have a different approach to solve our issue but did not want to leave this topic in the air. Might be also a good improvement for others.

 

Thanks

 

Issue Links

• causes: SLING-10167 MapEntries.loadAliases generates JCR queries with illegal absolute paths