[SLING-11439] resource resolver: fails to detect aborted vanity path query

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: ResourceResolver
• Assignee: Unassigned
• Reporter: Julian Reschke
• Created: 06/Jul/22 13:31
• Updated: 09/Sep/22 11:25

Description

With the introduction of the Oak query limit, JCR queries may get aborted when the result set size exceeds a certain value (currently by default 100000).

However:

https://github.com/apache/sling-org-apache-sling-jcr-resource/blob/604332e9be17378276685033bdbce54994dad8c1/src/main/java/org/apache/sling/jcr/resource/internal/helper/jcr/JcrNodeResourceIterator.java#L115-L134

So Apache Sling JCR Resource's API hides that exception, and thus resource resolver will happily startup with an incomplete cache.

Issue Links

• is related to: OAK-9929 OPTION (LIMIT ...) doesn't prevent RuntimeNodeTraversalException