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

Emmanuel Lecharny edited comment on DIRSERVER-1974 at 10/14/15 10:14 AM:
-------------------------------------------------------------------------

I have run the test using {{Mavibot}}, and the test passes green. This is 
clearly a {{JDBM}} problem...

Here is the config I used :

{code}
@CreateDS( name = "classDS",
        partitions = {
                @CreatePartition( 
                        type = MavibotPartition.class,
                        name = "example",
                        suffix = "dc=example,dc=com",
                        contextEntry = @ContextEntry(
                                entryLdif =
                                "dn: dc=example,dc=com\n" +
                                        "objectClass: domain\n" +
                                        "objectClass: top\n" +
                                        "dc: example\n\n"
                        ),
                        indexes = {
                                @CreateIndex(
                                    type = MavibotIndex.class,
                                    attribute = "objectClass" 
                                ),
                                @CreateIndex( 
                                    type = MavibotIndex.class,
                                    attribute = "dc" 
                                ),
                                @CreateIndex( 
                                    type = MavibotIndex.class,
                                    attribute = "ou" 
                                ),
                                @CreateIndex( 
                                    type = MavibotIndex.class,
                                    attribute = "uid" 
                                )
                        }
                )
        } )
{code}


was (Author: elecharny):
I have run the test using {{Maibot}}, and the test passes green. This is 
clearly a JDBM problem...

> 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)

Reply via email to