[
https://issues.apache.org/jira/browse/OAK-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552616#comment-13552616
]
Marcel Reutegger commented on OAK-535:
--------------------------------------
A bit off-topic, but still related because my optimization attempt lead me to
look into CommitCommandInstructionVisitor: wouldn't it make sense to simplify
visit(MoveNodeInstruction instruction) to:
{code}
String srcPath = instruction.getSourcePath();
// copy source to destination
visit(new CopyNodeInstructionImpl(instruction.getPath(),
srcPath, instruction.getDestPath()));
// delete source tree
visit(new RemoveNodeInstructionImpl(PathUtils.getParentPath(srcPath),
PathUtils.getName(srcPath)));
{code}
This would remove some duplicate code and should be about the same what the
current code does, right?
> 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: mergefixattempt.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
