[
https://issues.apache.org/jira/browse/SLING-12879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18113682#comment-18113682
]
Julian Reschke edited comment on SLING-12879 at 9/10/26 2:08 PM:
-----------------------------------------------------------------
bq. initialize the cache in the background; and while the cache is not
populated, the system resolves aliases directly (of course with an performance
impact).
That's how the system works already (and has all the time since we added the
background init).
was (Author: reschke):
bq. initialize the cache in the background; and while the cache is not
populated, the system resolves aliases directly (of course with an performance
impact).
That's how the system works (and has all the time since we added the background
init).
> ResourceResolver: add option to run alias initializer in background
> -------------------------------------------------------------------
>
> Key: SLING-12879
> URL: https://issues.apache.org/jira/browse/SLING-12879
> Project: Sling
> Issue Type: Sub-task
> Components: ResourceResolver
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Major
> Fix For: Resource Resolver 1.12.12, Resource Resolver 2.0.2
>
> Attachments: image-2026-09-08-13-34-48-536.png,
> image-2026-09-08-13-55-36-085.png, log-analyse-aem-vostra.json,
> resourceresolver-index-1.0.zip, slingResourceResolver-3.10.json
>
>
> This will add that option, but keep it disabled.
> For now it will only be tested in unit tests.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
