[
https://issues.apache.org/jira/browse/OAK-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13558622#comment-13558622
]
Mete Atamel commented on OAK-565:
---------------------------------
If we limit headRevId to trunk only, then how do you suggest that we mark the
revId of branch commits? Currently, branch commits are just like other commits
(with the exception of the branchId field) with revIds based on the headRevId
at the time commit was created but this would need to change if headRevId stays
the same during branch commits.
> CommitCommand readExistingNodes/mergeNodes called unnecessarily
> ---------------------------------------------------------------
>
> Key: OAK-565
> URL: https://issues.apache.org/jira/browse/OAK-565
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: mongomk
> Reporter: Mete Atamel
> Assignee: Mete Atamel
> Priority: Minor
> Attachments: commitcommandoptimization.patch
>
>
> CommitCommand/CommitCommandNew calls readExistingNodes and mergeNodes all the
> time. Instead, it should only call these methods when the base revision id is
> less than the head revision.
--
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
