[
https://issues.apache.org/jira/browse/DIRSERVER-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14950863#comment-14950863
]
lucas theisen edited comment on DIRSERVER-1974 at 10/9/15 5:55 PM:
-------------------------------------------------------------------
Just added an {{@Ingore}}'d unit test
({{testModifyRdnAndDeleteOldWithSearchInBetween}}) that shows how the index can
get corrupted after a rename operation. Basically if a new entry is created,
and searched for (using a {{search}}, not {{lookup}}), then {{rename}}d, then
searched for again, the entry will be found but it will report its {{dn}} as
the old value.
{code:title=revision 1707778}
$ svn commit -m "DIRSERVER-1974: added a unit test to demonstrate how rename
can corrupt the indexes"
Sending
server-integ/src/test/java/org/apache/directory/server/operations/modifydn/ModifyRdnIT.java
Transmitting file data .
Committed revision 1707778.
{code}
was (Author: [email protected]):
Just added an {{@Ingore}}'d unit test
({{testModifyRdnAndDeleteOldWithSearchInBetween}}) that shows how the index can
get corrupted after a rename operation. Basically if a new entry is created,
and searched for (using a {{search}}, not {{lookup}}), then {{rename}}d, then
searched for again, the entry will be found but it will report its {{dn}} as
the old value.
> Rename Operation Issue - ApacheDS
> ---------------------------------
>
> Key: DIRSERVER-1974
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1974
> 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
(v6.3.4#6332)
