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] [Closed] (DIRSERVER-1799) When deleting values from an existing entry, the presence index might get out of date
Date Tue, 19 Feb 2013 17:29:13 GMT

     [ https://issues.apache.org/jira/browse/DIRSERVER-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Emmanuel Lecharny closed DIRSERVER-1799.
----------------------------------------

    
> When deleting values from an existing entry, the presence index might get out of date
> -------------------------------------------------------------------------------------
>
>                 Key: DIRSERVER-1799
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1799
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 2.0.0-M10
>            Reporter: Emmanuel Lecharny
>            Priority: Critical
>             Fix For: 2.0.0-M11
>
>
> We use the reverse index to detect if an AT is not anymore present in an entry after
a modification ::
>             /*
>              * If no attribute values exist for this entryId in the index then
>              * we remove the presence index entry for the removed attribute.
>              */
>             if ( null == index.reverseLookup( id ) )
>             {
>                 presenceIdx.drop( modsOid, id );
>             }
> If the AT index does not have a reverse index, this operation will do nothing, and the
presence index will select entries which are not anymore useful.
> We should instead check if the Attribute is still existng after the modification, and
if not, remove it from the presence index without checking into it.

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

Mime
View raw message