jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bertrand Delacretaz <bdelacre...@apache.org>
Subject Re: Question about MVCC with MongoMK.
Date Fri, 06 Dec 2013 10:26:47 GMT

On Fri, Dec 6, 2013 at 11:12 AM, Jukka Zitting <jukka.zitting@gmail.com> wrote:
> ...The SegmentMK (with the MongoDB backend) can do this using the
> "hierarchical journal" feature.... The SegmentMK maintains one or more
> "journals" that each track the evolution of a particular branch of the
> repository. These branches would normally be automatically merged back
> to the "root" journal, but a particular deployment could easily
> disable automatic merging for a particular branch and use it for a
> purpose like the one you described....

Is there a way to tell the repository to start operating on such a
branch "forever" for a given client?

IIUC Ian's scenario, an application instance would tell Oak "create a
BEFORE_UPGRADE branch and start working on that from now on" so that
the content can be upgraded in the background and tested on other
application instances, before eventually merging the BEFORE_UPGRADE
branch back.

Is that possible today, or reasonably simple to implement? If yes that
would enable such a scenario with minimal application changes, which
sounds extremely useful.


View raw message