[
https://issues.apache.org/jira/browse/OAK-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348049#comment-15348049
]
Marcel Reutegger commented on OAK-4503:
---------------------------------------
bq. So, maybe, we should reset to 0 on rebase() and count again.
Yes, I think that's the correct fix. In-memory changes are re-applied with
{{ConflictAnnotatingRebaseDiff}} and the update count will then be updated
accordingly.
> Update count increases with rebase
> ----------------------------------
>
> Key: OAK-4503
> URL: https://issues.apache.org/jira/browse/OAK-4503
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, documentmk
> Affects Versions: 1.0, 1.2, 1.4
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Priority: Minor
> Fix For: 1.6
>
>
> The update count in {{DocumentRootBuilder}} increases with the number of
> changes in memory when {{rebase()}} is called. The update count should stay
> the same because a rebase does not affect the number of in-memory changes.
> This may lead to premature creation of a branch when pending changes are
> rebased too often. E.g. when Node.isLocked() is called frequently.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
