jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-2715) Improved join query performance
Date Wed, 01 Sep 2010 14:01:53 GMT

     [ https://issues.apache.org/jira/browse/JCR-2715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jukka Zitting updated JCR-2715:
-------------------------------

         Assignee: Jukka Zitting
    Fix Version/s: 2.2.0

I'm currently working on this, targeting the 2.2 release. The optimization plan I'm following
is:

1. Map single-selector queries directly to underlying Lucene queries, like we've so far done
for XPath and SQL1
2. Split join queries into a set of per-selector queries, and combine these partial results
into the join result set
3. When splitting join queries, use the results of the already executed left component query
to turn the join condition into an extra constraint for the right component query

> 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.


Mime
View raw message