directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kiran Ayyagari (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DIRSERVER-1579) Various problems using moddn operation
Date Sun, 22 May 2011 11:25:47 GMT

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

Kiran Ayyagari commented on DIRSERVER-1579:
-------------------------------------------

They are being set in the OperationalAttributeInterceptor. Do you see any issue with this?
otherwise can we close the issue?
(added a test case ClientModifyDnRequestTest testMoveAndRename() http://svn.apache.org/viewvc?rev=1125912&view=rev)

> 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-M1
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message