[
https://issues.apache.org/jira/browse/OAK-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-535:
---------------------------------
Attachment: FailFastMergeCommand.patch
I'd love to have a MergeCommand, which fails fast. See attached patch. But now
some tests fail, because they expect a MK implementation will consider
concurrent sibling creation as non-conflicting.
Removing the child node list in the parent node as proposed in OAK-586 would
resolve this issue.
> 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
> Assignee: Marcel Reutegger
> Attachments: FailFastMergeCommand.patch,
> 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
