[
https://issues.apache.org/jira/browse/SLING-11439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17564262#comment-17564262
]
Julian Reschke edited comment on SLING-11439 at 7/8/22 12:38 PM:
-----------------------------------------------------------------
My concern is that whatever page size I pick, it might break because
1. the query limit might be configured smaller, or
2. the page size is smaller than the number of search results sharing the same
vanity path
Both are edge cases, but I would feel better if I could write more robust code.
was (Author: reschke):
My concern is that whatever page size I pick, it might break because
1. the query limit might be considered smaller, or
2. the page size is smaller than the number of search results sharing the same
vanity path
Both are edge cases, but I would feel better if I could write more robust code.
> resource resolver: fails to detect aborted vanity path query
> ------------------------------------------------------------
>
> Key: SLING-11439
> URL: https://issues.apache.org/jira/browse/SLING-11439
> Project: Sling
> Issue Type: Bug
> Components: ResourceResolver
> Reporter: Julian Reschke
> Priority: Major
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
