[jira] Updated: (JCR-1196) Optimize queries for DescendantSelfAxisWeight/ChildAxisQuery

["Jukka Zitting (JIRA)" <ji...@apache.org>]

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

Jukka Zitting updated JCR-1196:
-------------------------------

          Component/s: jackrabbit-core
        Fix Version/s:     (was: 1.4)
    Affects Version/s:     (was: 1.3.3)
              Summary: Optimize queries for DescendantSelfAxisWeight/ChildAxisQuery  (was: Queries for DescendantSelfAxisWeight/ChildAxisQuery are currently very heavy and become slow pretty quickly)

> Optimize queries for DescendantSelfAxisWeight/ChildAxisQuery
> ------------------------------------------------------------
>
>                 Key: JCR-1196
>                 URL: https://issues.apache.org/jira/browse/JCR-1196
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: jackrabbit-core, query
>            Reporter: Ard Schrijvers
>
> A query like 
> /documents/en/news//*[@modificationDate] order by @modificationDate
> when  there are many nodes ( > 1.000) in  /documents/en/news becomes very slow. I think the bottleneck is in something like recursive filters in lucene. First off all I'll try to find some stastistics about the performance, and describe the bottleneck. After that, a solution must be found, where we need to keep in mind that 
> 1) these queries run faster and scale better (obviously)
> 2) moving a node must stay a cheap operation
> Also see:
> http://www.nabble.com/Search-performance--%3A-MultiIndex-tf4695559.html#a13421949

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.