[
https://issues.apache.org/jira/browse/SLING-13284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18101634#comment-18101634
]
Sagar Miglani commented on SLING-13284:
---------------------------------------
[~jsedding] I was able to reproduced it with following steps:
{code:xml}
setup: AEM 6.5.2 LTS
Steps:
1. Pause the async indexer via JMX
2. Modify the {{sling:alias}} array order on a node (simulates restart before
async indexer catches up)
3. Restart the resourceresolver bundle.
Result with 1.12.12:
ERROR [AliasInitializer] PagedQueryIterator unexpected query result in page 0,
property name 'sling:alias',got'ayacucho', last value was 'ayacucho-bamboo'
ERROR [AliasInitializer] AliasHandler Alias init failed
{code}
> PagedQueryIterator aborts alias/vanity cache init when async index is stale
> ---------------------------------------------------------------------------
>
> Key: SLING-13284
> URL: https://issues.apache.org/jira/browse/SLING-13284
> Project: Sling
> Issue Type: Bug
> Components: ResourceResolver
> Affects Versions: Resource Resolver 1.12.12
> Reporter: Sagar Miglani
> Assignee: Sagar Miglani
> Priority: Major
>
> {{PagedQueryIterator.getNext()}} throws {{QueryImplementationException}} when
> a row's live {{values[0]}} (read from repo) is less than the previous row's -
> aborting the entire alias/vanity cache build. This check assumes the async
> index ordering matches live property values, which cannot hold for an
> eventually-consistent async index.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
