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 mueller@adobe.com designates
 64.18.1.238 as permitted sender)
From: Thomas Mueller <mueller@adobe.com>
To: "oak-dev@jackrabbit.apache.org" <oak-dev@jackrabbit.apache.org>
Date: Tue, 18 Dec 2012 14:43:23 +0000
Subject: Re: Conflict handling in Oak
Thread-Topic: Conflict handling in Oak
Thread-Index: Ac3dLgXduIp1LVuoQ/KAEuatJ1RAXA==
Message-ID: <CCF63F02.38FFE%mueller@adobe.com>
In-Reply-To: <50D07F1E.9070704@apache.org>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.2.5.121010
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi,

>>>2) Allow inconsistent journals.
>>
>> I guess we don't want that. But the question is how close the journal
>>has
>> to match the original commit, specially "move" and "copy" operations. If
>> they need to be preserved (do they?), then it's complicated.
>
>There is no use for a journal which is not accurate. After all, if we
>consider implementing rebase (OAK-464) on top of the journal, it has to
>be accurate.

Yes, I think we should have a consistent journal, if we have a journal.

But the question is how close the journal has to match the original
commit, specially "move" and "copy" operations.

So, do "move" and "copy" operations need to be preserved, or can they be
converted to "add node" / "remove node"?


Regards,
Thomas