You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Serge Huber (JIRA)" <ji...@apache.org> on 2010/11/18 15:35:14 UTC
[jira] Commented: (JCR-2715) Improved join query performance
[ https://issues.apache.org/jira/browse/JCR-2715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933438#action_12933438 ]
Serge Huber commented on JCR-2715:
----------------------------------
Hello Jukka,
I was going over some performance tests, and I was wondering if the new code could be used for general SQL-2 queries ? I noticed that in the QueryObjectModelImpl we have the following check in the execute method:
if (JCR_JOIN_TYPE_INNER.equals(join.getJoinType())
&& join.getJoinCondition() instanceof EquiJoinCondition) {
But in the execution of the query engine we seem to be able to handle non-join cases in an optimized way that delegates back to the SQL-1 implementation.
Because it seems that in the case of simple queries like SELECT * FROM [nt:base] where CONDITION we are still going through non-optimized code that checks the constraints after loading all the results from Lucene.
Best regards,
Serge Huber.
> 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
>
>
> 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.