[
https://issues.apache.org/jira/browse/JCR-3477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13509885#comment-13509885
]
Michael Dürig commented on JCR-3477:
------------------------------------
I encountered this issue while investigating the root cause for JCR-3473. The
problem already occurs on running the query (no need to fetch the result
rows/nodes). I wonder what the original expectation for queries was. The
presence of LargeResultSetTest leads me to believe that such queries should
actually work but unfortunately JCR-3472 prevented us from detecting they
don't. If OTOH we don't except these queries to work, we need to find a way to
fix JCR-3473 without having to rely on queries.
> Lazy query result sets
> -----------------------
>
> Key: JCR-3477
> URL: https://issues.apache.org/jira/browse/JCR-3477
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core
> Reporter: Alex Parvulescu
> Priority: Minor
>
> Following JCR-3472, I'd like to open a discussion on what can be reasonably
> expected from a query that does/can do lazy fetching of results.
> Creating ~110k nodes and fetching them all looks like it goes in the vicinity
> of 400mb of memory, so the default 256mb setup for tests is not sufficient to
> run such a test, as we've already seen on JCR-3472.
> What are the expectations around lazy loading and queries that can
> potentially hit a high number of nodes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
