[
https://issues.apache.org/jira/browse/OAK-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13555104#comment-13555104
]
Mete Atamel commented on OAK-535:
---------------------------------
Yeah I tried to minimize FetchCommit and looping as much as I can and I think
overlapping affected paths should be detected with this algorithm. Every time
an affected path is detected for branch/trunk, it's checked against
trunk/branch set. If trunk/brach set does not have it yet, then the affected
path will be put into branch/trunk set and checked again for trunk/branch
against branch/trunk set. Since we fetch all commits from branch root until
latest commit, it should contain all the relevant affected paths. But if you
can think of a case where the algorithms fails, please let me know.
> 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
