[
https://issues.apache.org/jira/browse/JCR-2715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967005#action_12967005
]
Jukka Zitting commented on JCR-2715:
------------------------------------
> Jukka, is there a reason why we load all the data in the SQL-2/QOM
> implementations at query execution time?
The SQL2/JQOM code needs to take joins and some new constraint types into
account, which makes it easiest to simply load the full result set into memory
during execute(). In practice this only causes problems when your query matches
lots of rows but you're only interested in some of them (see JCR-2830).
> Improved join query performance
> -------------------------------
>
> Key: JCR-2715
> URL: https://issues.apache.org/jira/browse/JCR-2715
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core, query
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Fix For: 2.2.0
>
> Attachments: 2010-11-30_PM-04-55-23.zip, SQL2SearchTest.png,
> ThreeWayJoinTest.png, TwoWayJoinTest.png
>
>
> Our current implementation of SQL2 join queries does not perform very well on
> pretty much any non-trivial data set.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
