You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2013/06/13 10:40:20 UTC

[jira] [Commented] (DIRSERVER-1854) Indexes for entry corrupted after replace modification

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

Emmanuel Lecharny commented on DIRSERVER-1854:
----------------------------------------------

I have done some test on a 8000 entries base, modifying the CN (replace), and the filter still works whe it's like (cn=AAA*). Can you check if the (cn=User*) works ? The (cn=*) filter uses another index, Im currenty checking it. 
                
> Indexes for entry corrupted after replace modification
> ------------------------------------------------------
>
>                 Key: DIRSERVER-1854
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1854
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 2.0.0-M12
>         Environment: Windows x64, Java 1.6.0_32, ApacheDS API 1.0.0-M17
>            Reporter: Carlo Accorsi
>
> We have several attributes indexed on a custom partition. The first time the entry is created and saved, the attribute is searchable with a wildcard. For example, if there are two entries with the following CN's: 
> cn: User One
> cn: User Two
> the search cursor for (cn=*) will return two entries. If the cn on one of the entries is changed with a replace modification, (cn=*) will not include the entry in a result.  This behavior is observed with other indexed attributes as well.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira