Description
Problem Statement
When creating queries, developers can specify the limit / offset by calling the appropriate method on the javax.jcr.Query object. However there is not an option to do so in the body of the query statement itself.
Therefore, when either using an existing UI or existing API that does not support setting these values, it's possible to construct a query that runs against indexed data but still fails due to reading too many nodes.
Solution
Add support for setting the offset / limit via options
Attachments
Issue Links
- fixes
-
SLING-11230 Support Limit and Offset via JcrResourceProvider / findResources
- Resolved
- is related to
-
SLING-11230 Support Limit and Offset via JcrResourceProvider / findResources
- Resolved
- relates to
-
SLING-11342 resource resolver: use paged query for vanity paths (optionally?)
- Resolved
- links to