[SLING-11342] resource resolver: use paged query for vanity paths (optionally?)

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Component/s: ResourceResolver
• Assignee: Unassigned
• Reporter: Julian Reschke
• Created: 24/May/22 08:01
• Updated: 01/Sep/23 13:19
• Resolved: 31/Jan/23 11:59

Description

In recent Oak versions, queries will be aborted if they exceed a fixed limit of hits.

We need to do paged queries instead.

Issue Links

• duplicates: SLING-11581 use keyset pagination for vanity path query
• is blocked by: OAK-9625 Support ordered index for first value of a multi-valued property, node name, and path
• is related to: OAK-9740 Add Support For Limit / Offset Options in Queries
• is superceded by: SLING-11581 use keyset pagination for vanity path query
• relates to: SLING-12017 resource resolver: add fallback when paged query fails due to missing index