Re: PresenceIndex : why is it updated only for indexed AT ?

Hi Emmanuel, On Wed, Mar 21, 2012 at 5:21 PM, Emmanuel Lécharny elecha...@gmail.comwrote: Hi guys, as I was reviewing the presenceIndex usage this morning, I found that we only add entries in this index if the AT is indexed. This is correct and was explicitly intended for this exact

[index] Presence index usage

Hi guys, I will split my mails about index in smaller mails, in order to focus on one element at a time. Let's first talk about the presence index. Yesterday, I posted a question about the need to restrain this index to hold only the AT which are indexed. Alex explain that it was rational

Re: [index] Presence index usage

On Thu, Mar 22, 2012 at 04:40:17PM +0100, Emmanuel Lécharny wrote: Hi guys, I will split my mails about index in smaller mails, in order to focus on one element at a time. Let's first talk about the presence index. Yesterday, I posted a question about the need to restrain this index to

Re: [index] Presence index usage

Le 3/22/12 5:11 PM, h...@symas.com a écrit : On Thu, Mar 22, 2012 at 04:40:17PM +0100, Emmanuel Lécharny wrote: Hi guys, I will split my mails about index in smaller mails, in order to focus on one element at a time. Let's first talk about the presence index. Yesterday, I posted a question

Re: [index] Presence index usage

On Thu, Mar 22, 2012 at 05:28:50PM +0100, Emmanuel Lécharny wrote: Le 3/22/12 5:11 PM, h...@symas.com a écrit : On Thu, Mar 22, 2012 at 04:40:17PM +0100, Emmanuel Lécharny wrote Now, if we consider the fact that having all the AT stored in the index will allow us to know what will be the

[index] reverse index usage for user attributes

Hi, Currently, we create a forward and a reverse index for each index attribute. The forward index is used when we annotate a filter, searching for the number of candidate it filters. The reverse index usage is a bit more subtile. Let's consider a filter like (cn=jo*). As we don't have any

[index] RDN

Hi, a second mail about index, specifically those related to the manipulation of the DN. RDN index - First of all, let's present the data structure used for the Rdn index. It's not exactly a RDN index, as the key is a composite structure : the ParentIdAndRDN (it contains the entry

[index] OneLevel and SubLevel index

Hi, one last mail... I will just mention that we alreadu discussed this mater (ie should we keep oneLevel and sublevel index) last year with Stefan, and he thinks that we can get rid of those two guys :

[Index] Alias

Hi, I forgot to mention the alias index. Currently, we use three indexes : - alias - oneAlias - subAlias I have not yet investigated these index and how they are used, so if someone has a good understanding on how they are used and how we can get them improved, that would be very welcomed.

[Index] Defining indexes without a reverse table

Hi, currently, all the index we create have two underlying tables : forward and reverse. As we have seen, it's sometime spurious to have a reverse index (like for the presence index, the entryUUID or ObjectClass) W can modify slightly the implementation to have index instance having only a