Hi, On Wed, Jan 8, 2014 at 9:29 AM, Michael Dürig <[email protected]> wrote: > Not any more I think. This might be a leftover from the time rebasing was > handled on the Tree/Root layer. Today it would be better to leave this kind > of optimisation to the layers actually performing the rebase.
Agreed. > 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. BR, Jukka Zitting
