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] [Commented] (DIRSERVER-1974) Rename Operation Issue - ApacheDS
Date Mon, 01 Jul 2019 09:28:00 GMT

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

Emmanuel Lecharny commented on DIRSERVER-1974:
----------------------------------------------

Coming back to this issue (4 years... hmmm...)

Switching back to JDBM, the {{testRenameWithALotOfDummiesAndSomeCustomAttributes}} fail in
the first loop. Stepping through have it working.
What seems to happen is that it takes a bit of times for the DN to be updated:

{noformat}
Correct entry found 1 :uid=myra-ellen-amos,ou=people,dc=example,dc=com/uid: myra-ellen-amos
Wrong entry found 2 :uid=myra-ellen-amos,ou=people,dc=example,dc=com/uid: tory-amos

Correct entry found 1 :uid=myra-ellen-amos,ou=people,dc=example,dc=com/uid: myra-ellen-amos
Correct entry found 2 :uid=tory-amos,ou=people,dc=example,dc=com/uid: tory-amos
...
{noformat}

Now, if I add a 100ms sleep in the loop, the test works just fine :/ There is something time
dependent which is quite nasty going on.

> Rename Operation Issue - ApacheDS
> ---------------------------------
>
>                 Key: DIRSERVER-1974
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1974
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: jdbm, 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
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
For additional commands, e-mail: dev-help@directory.apache.org


Mime
View raw message