directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DIRSERVER-1579) Various problems using moddn operation
Date Wed, 22 Feb 2012 14:35:49 GMT

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

Emmanuel Lecharny resolved DIRSERVER-1579.
------------------------------------------

    Resolution: Fixed

AFAICT, the operational attributes are now injected into the modified entry.
                
> Various problems using moddn operation
> --------------------------------------
>
>                 Key: DIRSERVER-1579
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1579
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: ldap
>    Affects Versions: 2.0.0-RC1
>            Reporter: Stefan Seelmann
>             Fix For: 2.0.0-RC1
>
>
> Operational attributes (modifiersName, modifyTimestamp) are not set when using moveAndRename()
operation
> There is no check in SchemaInterceptor for the moveAndRename() operation.
> In the backend the rename() operation works with the cloned entry which was modified
in the interceptor chain. The SchemaInterceptor applied all modifications (new DN, adds new
RDN attributes, delete old RDN attributes if requested) in the cloned entry. Thus the maintenence
of the indexes in the backend doesn't work.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message