[
https://issues.apache.org/jira/browse/SLING-11439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17564190#comment-17564190
]
Thomas Mueller edited comment on SLING-11439 at 7/8/22 9:28 AM:
----------------------------------------------------------------
> Paging by default will make things more complicated
Yes, but I think that's just the price to pay for a modern API... With modern
API, I mean an API that can works well in a remote setting. Returning a huge
result set doesn't work well in a remote setting: it either requires state on
the server side, or it requires a huge and slow response. Both it not good.
Similar to web pages: they need to be returned quickly, and it's better if they
don't require state on the server side. (Keyset pagination is state on the
client side... that part is fine.)
was (Author: tmueller):
> Paging by default will make things more complicated
Yes, but I think that's just the price to pay for a modern API... With modern
API, I mean an API that can works well in a remote setting. Returning a huge
result set doesn't work well in a remote setting: it either requires state on
the server side, or it requires a huge and slow response. Both it not good.
Similar to web pages: they need to be returned quickly, and it's better if they
don't require state on the server side. (Pagination is state on the client
side... that part is fine.)
> 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)
