[
https://issues.apache.org/jira/browse/SLING-11800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17874009#comment-17874009
]
Julian Reschke edited comment on SLING-11800 at 8/15/24 4:50 PM:
-----------------------------------------------------------------
The proposed solution is to replicate what we did for vanity paths: running the
cache init async. The problem with that - other than for vanity paths - is that
the fallback query we would need to use during cache init is much slower.
was (Author: reschke):
We dismissed the idea of caching aliases in a persisted resource for vanity
paths, due to complexity (such as service user being needed to write it, and
lack of compleness when new nodes are added while the node restarts).
The proposed solution is to replicate what we did for vanity paths: running the
cache init async. The problem with that - other than for vanity paths - is that
the fallback query we would need to use during cache init is much slower.
> resource resolver: optionally run initial alias query asynchronously
> --------------------------------------------------------------------
>
> Key: SLING-11800
> URL: https://issues.apache.org/jira/browse/SLING-11800
> Project: Sling
> Issue Type: Improvement
> Components: ResourceResolver
> Affects Versions: Resource Resolver 1.8.6
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Major
>
> ...to avoid slow startup in presence of many alias resources.
> (add OSGi switch and keep the old behavior as default for now)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
