directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (DIRSERVER-2077) Provide tools to migrate the config or the data between releases
Date Wed, 30 Aug 2017 14:01:14 GMT

    [ https://issues.apache.org/jira/browse/DIRSERVER-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16147265#comment-16147265
] 

Emmanuel Lecharny edited comment on DIRSERVER-2077 at 8/30/17 2:00 PM:
-----------------------------------------------------------------------

Ok, problem fixed : the {{LdifReader}} was correctly fixed but in the case of an empty human
readable attribute (like {{ads-baseDn}}), we were trying to store a {{byte[]}} instead of
{{""}} in the attribute, which led to a (silentely ignored) error.

I fixed that with {{commit 1c8afb1cffff011d6dc16e1d2ab369cd70d49d49}} and {{commit d81e587885309f1f5b5e5efbf30220e8c7c61b1d}}
for the previous fix.

It's still in a branch, I need more tests before moving those fixes to trunk.


was (Author: elecharny):
Ok, problem fixed : the {{LdifReader}} was correctly fixed but in the case of an empty human
readable attribute (like {{ads-baseDn}}), we were trying to store a {{byte[]}} instead of
{{""}} in the attribute, which led to a (silentely ignored) error.

I fixed that with {{commit 1c8afb1cffff011d6dc16e1d2ab369cd70d49d49}} and {{commit d81e587885309f1f5b5e5efbf30220e8c7c61b1d}
for the previous fix.

It's still in a branch, I need more tests before moving those fixes to trunk.

> Provide tools to migrate the config or the data between releases
> ----------------------------------------------------------------
>
>                 Key: DIRSERVER-2077
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-2077
>             Project: Directory ApacheDS
>          Issue Type: Task
>    Affects Versions: 2.0.0-M20
>            Reporter: Emmanuel Lecharny
>            Priority: Critical
>             Fix For: 2.0.0-M24
>
>
> We have been lazy in the past, by not provided tools to migrate from one version to the
other, simply because they were milestones.
> There are three things we need to migrate :
> - configuration 
> - schemas
> - data
> for each of those data, we have to provide a tool that helps the migration from one version
to the next one.
> Ideally, this should be cumulative : ie, migrating from N to, say, N+3 should migrate
those data from N to N+1, then N+1 to N+2 and finally N+2 to N+3



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message