sagarmiglani opened a new pull request, #224: URL: https://github.com/apache/sling-org-apache-sling-resourceresolver/pull/224
…ery results The ordering check in PagedQueryIterator compared live property values (read from the repository) against the sort order delivered by an async Lucene index. Since async indexes are eventually consistent, their sort order can lag behind the current repository state after a property write. The previous behavior treated this lag as a fatal error and aborted the entire alias/vanity cache build, leaving alias resolution non-functional until a manual reindex + restart. Demote the two throws to log.warn and continue processing. The row contains a valid alias/vanity value that should be cached regardless of sort position. This also addresses the vanity-path variant (SLING-13248). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
