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] [Commented] (JCR-2989) Support for embedded index aggregates
Date Thu, 16 Jun 2011 10:05:47 GMT

    [ https://issues.apache.org/jira/browse/JCR-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050327#comment-13050327

Alex Parvulescu commented on JCR-2989:

Yes, on update the structure will be traversed up, so the parents will be updated. For each
change, you'll have as many updates as there are levels of inclusion.

But I'm not sure how big this problem is. I'd say it depends on the number of levels you hierarchy
has, and the number of fields a node has indexed. But you can easily abuse both :)

I'll tweak the code a bit so that it tries to optimize the upward update. Basically when checking
a node's root aggregate, if this is already on the update list, stop there, as all its parents
are already included in this update.

I agree on having a soft rule in place for recursive aggregates (lets say max 5 levels deep),
but I think having a recursive=true rule doesn't help the average copy-paste-from-the-wiki
user :)  
(and by the way that includes me too, as the docs are not excellent ;)

> Support for embedded index aggregates
> -------------------------------------
>                 Key: JCR-2989
>                 URL: https://issues.apache.org/jira/browse/JCR-2989
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>            Reporter: Alex Parvulescu
>            Assignee: Alex Parvulescu
>            Priority: Minor
>         Attachments: JCR-2989.patch
> Index aggregates could contain other index aggregates. JR should be able to handle a
complete hierarchy of aggregates. 
> I'm working on a patch.

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


View raw message