Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (nike.apache.org: domain of elecharny@gmail.com designates
 209.85.212.182 as permitted sender)
Message-ID: <5506937A.9090508@gmail.com>
Date: Mon, 16 Mar 2015 09:25:30 +0100
From: =?UTF-8?B?RW1tYW51ZWwgTMOpY2hhcm55?= <elecharny@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
 rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: Re: [Studio] Configuration editor doesn't preserve operational
 attributes
References: <55055028.70207@stefan-seelmann.de>
In-Reply-To: <55055028.70207@stefan-seelmann.de>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

Le 15/03/15 10:26, Stefan Seelmann a écrit :
> Hi,
>
> I work on DIRSTUDIO-1016 and changing the configuration editor to
> support multi-file LDIF configuration partition.
>
> What I found with the current editor: if we open the config.ldif, make
> some changes, and save it, we just rewrite the whole file and all
> operational attributes (entryUUID, entryCSN) are newly created. For sake
> of simplicity I'd implement saving to multi-file LDIF partition the same
> way (delete the conf directory and recreate it).
>
> But I wonder if that is ok? Is the config partition meant to be
> replicated (then it may be a problem)?

The current implementation (ie one biug file) is problematic during
replicating just because we update all the entryCSN/entryUUID : that
means everything get replicated...

The idea of multiple files for config is to avoid having to replicate
everything, but just updating the entryCSN of the modified entries and
only those.

So with respect to this constraint, I'd say that we should be careful
not to update anything that hasn't be changed, which might require some
extra work...

Thanks !