You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by "Alex Parvulescu (Updated) (JIRA)" <ji...@apache.org> on 2011/11/29 12:27:40 UTC

[jira] [Updated] (JCR-3160) Session#move doesn't trigger rebuild of parent node aggregation

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

Alex Parvulescu updated JCR-3160:
---------------------------------

    Attachment: JCR-3160.patch

attaching patch.

I have removed what looked like an optimisation.
But I can't remember what the reason for this optim was (most probably performance related).

If a node is both in the removed and in the added sets then it is definitely a 'move' operation. By removing it from the 'removedIds' set, the aggregation info would not be updated for the given node.


                
> Session#move doesn't trigger rebuild of parent node aggregation
> ---------------------------------------------------------------
>
>                 Key: JCR-3160
>                 URL: https://issues.apache.org/jira/browse/JCR-3160
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>            Reporter: Alex Parvulescu
>            Assignee: Alex Parvulescu
>            Priority: Minor
>         Attachments: JCR-3160.patch
>
>
> The summary says it all.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira