Return-Path: X-Original-To: apmail-directory-dev-archive@www.apache.org Delivered-To: apmail-directory-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9FF8310A21 for ; Wed, 19 Jun 2013 07:17:26 +0000 (UTC) Received: (qmail 25379 invoked by uid 500); 19 Jun 2013 07:17:26 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 25188 invoked by uid 500); 19 Jun 2013 07:17:25 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 24631 invoked by uid 99); 19 Jun 2013 07:17:23 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Jun 2013 07:17:23 +0000 Date: Wed, 19 Jun 2013 07:17:23 +0000 (UTC) From: "Emmanuel Lecharny (JIRA)" To: dev@directory.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (DIRSERVER-1854) Indexes for entry corrupted after replace modification MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DIRSERVER-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Lecharny resolved DIRSERVER-1854. ------------------------------------------ Resolution: Fixed I have added some tests for the various use case, it seems to be fixed with the previous commit. > 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