jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mete Atamel (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OAK-535) MergeCommand reads complete tree into memory
Date Wed, 16 Jan 2013 14:30:12 GMT

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

Mete Atamel updated OAK-535:

    Attachment: mergecommandoptimization.patch

I'm attaching a further optimization to Marcel's initial MergeCommand optimization. Basically,
even if there have been commits on trunk since the branch was created, MergeCommand now checks
whether those commits are conflicting with branch commits. If not, it simply reapplies branch
commits to trunk.
> MergeCommand reads complete tree into memory
> --------------------------------------------
>                 Key: OAK-535
>                 URL: https://issues.apache.org/jira/browse/OAK-535
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: mongomk
>    Affects Versions: 0.5
>            Reporter: Marcel Reutegger
>         Attachments: mergecommandoptimization.patch, mergefixattempt.patch, movepatch.diff,
moves-in-commit.patch, OAK-535.patch
> Merging commits to a branch back to head in MongoMK calls MergeCommand, which reads the
complete tree into memory. The more content is in the repository, the longer it takes to store
even a simple update as a property change.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message