jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-1365) Query path constraints like foo//*/bar do not scale
Date Wed, 20 Feb 2008 13:45:43 GMT

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

Marcel Reutegger resolved JCR-1365.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5

Implemented more performance optimizations. If the last location step is a child or descendant-or-self
axis with a node test that matches any node, the implementation now uses context query result
in conjunction with the regular API to find the matching nodes.

This again gives a performance improvement of a factor of 7 compared to 'series 2' and still
a factor of 2 compared to 'series 3', where the cacheSize was increased significantly.

svn revision: 629453

> Query path constraints like foo//*/bar do not scale
> ---------------------------------------------------
>
>                 Key: JCR-1365
>                 URL: https://issues.apache.org/jira/browse/JCR-1365
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: jackrabbit-core
>            Reporter: Marcel Reutegger
>            Priority: Minor
>             Fix For: 1.5
>
>         Attachments: Book1_25575_image001.png
>
>
> To resolve the * step the LuceneQueryBuilder currently creates a MatchAllQuery and checks
every node for a foo ancestor. Instead, it should search for bar nodes and check for foo ancestors
with at least one arbitrary hierarchy level in between.

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