[SLING-11799] use keyset pagination for sling:alias query

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Resource Resolver 1.11.6
• Component/s: ResourceResolver
• Assignee: Julian Reschke
• Reporter: Julian Reschke
• Created: 08/Mar/23 15:19
• Updated: 15/Aug/24 16:43
• Resolved: 09/Jan/24 09:31

Description

Similar to what was done for vanity paths (SLING-11581), we should use keyset pagination for queries for sling:alias.

This would work the same in principle, however we should keep in mind that - due to the different type of data - we may have way more duplicates, so in edge cases the pages might be bigger than expected. However, every size reduction of "results of a single query" should help.

Issue Links

• is a clone of: SLING-11581 use keyset pagination for vanity path query
• is blocked by: SLING-12205 ResourceResolver: switch sling:alias query to JCR-SQL2
• is related to: SLING-12225 resource resolver: revise documentation and naming of system properties for query paging
• relates to: SLING-12384 ResourceResolver: paged query for sling:alias will miss entries
• relates to: SLING-12204 ResourceResolver: refactor PagedQueryIterator for re-use
• links to: GitHub Pull Request #110
• links to: GitHub Pull Request #111