Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Date: Sat, 7 Feb 2015 15:31:34 +0000 (UTC)
From: "Kiran Ayyagari (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Message-ID: <JIRA.12773228.1423322970000.291063.1423323094400@Atlassian.JIRA>
In-Reply-To: <JIRA.12773228.1423322970000@Atlassian.JIRA>
References: <JIRA.12773228.1423322970000@Atlassian.JIRA>
 <JIRA.12773228.1423322970840@arcas>
Subject: [jira] [Updated] (DIRSERVER-2050) Move configuration from single
 LDIF to multiple LDIF structure
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DIRSERVER-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kiran Ayyagari updated DIRSERVER-2050:
--------------------------------------
    Description: 
Until now configuration is being stored in a single LDIF file, this is leading to
some performance issues especially when used in cases like the one mentioned [here|http://markmail.org/thread/j4c4u2mwwhfouqih]. 

Now the solution is to split configuration into multiple LDIF files, which will still
allow the users to edit configuration by hand when needed.

This move is backward compatible, in the sense that after upgrading to M20 
the existing *config.ldif* file data will be stored in the new format 
and the file will be preserved under the name *config.ldif_migrated*.
This new file will never be used by the server again.


  was:
Until now configuration is being stored in a single LDIF file, this is leading to
some performance issues especially when used in cases like the one mentioned [here|http://markmail.org/thread/j4c4u2mwwhfouqih]. 

Now the solution is to split configuration into multiple LDIF files, which will still
allow the users to edit configuration by hand when needed.

This move is backward compatible, in the sense that after upgrading to M20 
the existing {code}config.ldif{code} file data will be stored in the new format 
and the file will be preserved under the name {code}config.ldif_migrated{code}.
This new file will never be used by the server again.


> Move configuration from single LDIF to multiple LDIF structure
> --------------------------------------------------------------
>
>                 Key: DIRSERVER-2050
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-2050
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>    Affects Versions: 2.0.0-M19
>            Reporter: Kiran Ayyagari
>            Assignee: Kiran Ayyagari
>             Fix For: 2.0.0-M20
>
>
> Until now configuration is being stored in a single LDIF file, this is leading to
> some performance issues especially when used in cases like the one mentioned [here|http://markmail.org/thread/j4c4u2mwwhfouqih]. 
> Now the solution is to split configuration into multiple LDIF files, which will still
> allow the users to edit configuration by hand when needed.
> This move is backward compatible, in the sense that after upgrading to M20 
> the existing *config.ldif* file data will be stored in the new format 
> and the file will be preserved under the name *config.ldif_migrated*.
> This new file will never be used by the server again.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)