[jira] [Commented] (OAK-4503) Update count increases with rebase

["Vikas Saurabh (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OAK-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348044#comment-15348044 ] 

Vikas Saurabh commented on OAK-4503:
------------------------------------

bq. The update count should stay the same because a rebase does not affect the number of in-memory changes.

Actually, I think rebase() does change in-memory count ... the only example I can think of is creation of intermediate nodes under property indices. So, maybe, we should reset to 0 on rebase() and count again.

> 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)