[
https://issues.apache.org/jira/browse/SLING-11439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17564181#comment-17564181
]
Thomas Mueller commented on SLING-11439:
----------------------------------------
> (To make things worse, we don't have a way to detect whether
> https://issues.apache.org/jira/browse/OAK-9625 is supported at runtime)
Well, it is quite easy to detect: You can just try to run this query, and if it
fails with a syntax exception, run the old code, or a simpler query without
"jcr:first", for example:
{noformat}
/jcr:root//element(*, nt:base)[@alias]
{noformat}
(Which might be the query that is used today.)
> 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)
