directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "lucas theisen (JIRA)" <>
Subject [jira] [Commented] (DIRSERVER-1974) Rename Operation Issue - ApacheDS
Date Mon, 12 Oct 2015 18:44:06 GMT


lucas theisen commented on DIRSERVER-1974:

Ok, I finally have a unit test to demonstrate this issue: {{server-integ/src/test/java/org/apache/directory/server/operations/modifydn/}}.
 It was committed here:
$ svn commit -m "moved integration test showing rename issue into separate class"
Adding         server-integ/src/test/java/org/apache/directory/server/operations/modifydn/
Sending        server-integ/src/test/java/org/apache/directory/server/operations/modifydn/
Adding         server-integ/src/test/resources/dirserver_1974_it.ldif
Sending        server-integ/src/test/resources/
Transmitting file data ....
Committed revision 1708198.

This issue appears to be triggered by combination of 4 factors...  
# a large set of initial elements (1000 users)
# a custom attribute
# a custom index
# a loop to add, rename, delete the same user up to 100 times.

> Rename Operation Issue - ApacheDS
> ---------------------------------
>                 Key: DIRSERVER-1974
>                 URL:
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: ldap
>    Affects Versions: 2.0.0-M15
>         Environment: Window server 2008 R2
>            Reporter: Mohd Usman
>            Priority: Blocker
>              Labels: build, features, patch
>         Attachments: ApacheDSSchemaBrowser.png, CNAttributeInSchema.png, PostRename.png,
PreRename.png, SchemaViewerLDAPAdminTool.png
>   Original Estimate: 168h
>  Remaining Estimate: 168h
> Whenever we perform Rename operation on an object entry (let’s say Person object),
the person gets renamed successfully but the issue is that the old value of the person object
still remains.
> The ‘cn’ attribute contains two values now - old value and also the new value.
> Example:
> I have created a person object with DN "cn=person,ou=Apache,dc=example,dc=com" and I
want to rename this entry to "cn=person_Rename,ou=Apache,dc=example,dc=com".
> The rename operation executes successfully and the person is renamed to "cn=person_Rename,ou=Apache,dc=example,dc=com".

> But, the ‘cn’ attribute now contains 
> “person”
> “person_Rename”.
> When verified the schema, ‘cn’ attribute show as ‘single valued’ but after performing
the rename operation – the ‘cn’ becomes ‘multi-valued’ and contains two values.
> This an issue with Apache directory which needs to be resolved. Also find the screenshots
attached for your reference. Please look into the same.

This message was sent by Atlassian JIRA

View raw message