[
https://issues.apache.org/jira/browse/JCR-2715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985105#action_12985105
]
Manfred Sattler commented on JCR-2715:
--------------------------------------
Hello
i have attached a script.
The execution gives different results in the new implemention and the old
one(before 2.2).
Also some annotiations:
With large Nodeset in the left Side of left outer join the executiontime is
very big. (Minutes)
This query is not possible:
Select * from [sling:SamplePage] as c left outer join [sling:SampleContent] as
a on ISDESCENDANTNODE(a,c) where contains(c.key1,'value1') or
contains(a.key1,'value1')
I think this is a correct query and in the old implementation it works.
I have also attached an hacked SQL2-Code from 2.1.
This implementation is very fast and gives the same Results as before 2.2.
You can dropin this in 2.3-Source tree and it works
> 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.
