You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Kiran Ayyagari (JIRA)" <ji...@apache.org> on 2015/02/07 16:35:34 UTC

[jira] [Resolved] (DIRSERVER-2050) Move configuration from single LDIF to multiple LDIF structure

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

Kiran Ayyagari resolved DIRSERVER-2050.
---------------------------------------
    Resolution: Fixed

Added here http://svn.apache.org/r1658068.

> 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)