[jira] [Comment Edited] (SLING-11439) resource resolver: fails to detect aborted vanity path query

["Thomas Mueller (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-11439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17563302#comment-17563302 ] 

Thomas Mueller edited comment on SLING-11439 at 7/6/22 3:35 PM:
----------------------------------------------------------------

> exposing the exception in some way.

For example, by throwing a RuntimeException.

I don't have a strong opinion on this. Other than: it is important that the problem itself is fixed. The main problems, for me, are:
* It blocks startup for a long time.
* It doesn't properly read all the entries.


was (Author: tmueller):
> exposing the exception in some way.

For example, by throwing a RuntimeException.

I don't have a strong opinion on this. (Other than: it is important that the problem itself is fixed.)

> 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)