[
https://issues.apache.org/jira/browse/OAK-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13558636#comment-13558636
]
Marcel Reutegger commented on OAK-565:
--------------------------------------
bq. mark the revId of branch commits
I'm not sure I understand what you mean with 'mark'. Do you mean what the
current head is of a branch? I'd say it's simply the highest revId of the
commits for a given branch. Hmm, but I think I now understand what you mean.
There may be a problem when we have concurrent commits to a branch. Not sure if
that's permitted though... With concurrent branch commits we'd indeed need
something like the sync collection to coordinate the commits. But I don't think
so for serialized 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
