Hi, On Wed, Jan 8, 2014 at 9:49 AM, Jukka Zitting <[email protected]> wrote: > On Wed, Jan 8, 2014 at 9:29 AM, Michael Dürig <[email protected]> wrote: >> However, removing this check seems to uncover a problem with the SegmentMK: >> it makes org.apache.jackrabbit.oak.core.MutableTreeTest#modifiedAfterRebase >> fail for that fixture. For some reason the status of a modified node changes >> to existing after a rebase, which is wrong. >> >> Jukka, would you be able to look into this? > > Sure.
The problem turned out to be in the MutableNodeState.isModified() check, triggered by the way the SegmentMK automatically purges uncommitted changes. Fixed in revision 1558270. BR, Jukka Zitting
