jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vikas Saurabh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-4503) Update count increases with rebase
Date Wed, 06 Jul 2016 13:09:11 GMT

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

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

[~mreutegg], is it ok if I backport this? Do we want OAK-4536 as well?

> 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
>              Labels: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4
>             Fix For: 1.6, 1.5.5
>
>
> 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)

Mime
View raw message