jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Parvulescu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (JCR-2918) Avoid unnecessary index reader calls when using aggregate definitions
Date Tue, 05 Jul 2011 10:17:16 GMT

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

Alex Parvulescu updated JCR-2918:

       Resolution: Fixed
    Fix Version/s: 2.3.0
         Assignee: Alex Parvulescu
           Status: Resolved  (was: Patch Available)

Fixed on trunk in revision 1142919, and on 2.2 in revision 1142926

by the way, I used a wrong rev number in the comment for the 2.2 commit 

> Avoid unnecessary index reader calls when using aggregate definitions
> ---------------------------------------------------------------------
>                 Key: JCR-2918
>                 URL: https://issues.apache.org/jira/browse/JCR-2918
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core
>            Reporter: Marcel Reutegger
>            Assignee: Alex Parvulescu
>            Priority: Minor
>             Fix For: 2.2.8, 2.3.0
>         Attachments: JCR-2918.patch
> SearchIndex.retrieveAggregateRoot(Set<NodeId> removedIds, Map<NodeId, NodeState>
map) identifies aggregate root nodes based on removed nodes and aggregate rules defined in
the indexing configuration. This process requires index lookups. The method can be optimized
for the case when no nodes are removed and an unnecessary call to the index reader can be

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message