Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: oak-dev@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of jukka.zitting@gmail.com
 designates 209.85.219.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAH=Gj-kOXPW7-ztzOFZ-LZzoaVtXsehy+qN4HLcGUaAcZ5+uaQ@mail.gmail.com>
References: 
 <CAH=Gj-kOXPW7-ztzOFZ-LZzoaVtXsehy+qN4HLcGUaAcZ5+uaQ@mail.gmail.com>
From: Jukka Zitting <jukka.zitting@gmail.com>
Date: Fri, 6 Dec 2013 05:12:09 -0500
Message-ID: 
 <CAOFYJNZRfvsFNqm9hyyi1=5o1D7BzQ3O3-r=oggq_kz5BO-MUg@mail.gmail.com>
Subject: Re: Question about MVCC with MongoMK.
To: Oak devs <oak-dev@jackrabbit.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

Hi,

On Thu, Dec 5, 2013 at 9:43 PM, Ian Boston <ieb@tfd.co.uk> wrote:
> Is it possible to branch an Oak repository and maintain a detached
> root node for a period of time that one or more Oak instances attached
> to a MongoDB instance can follow for a short period of time before
> merging the "branch" back into the main tree ?

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.

BR,

Jukka Zitting