Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (nike.apache.org: domain of elecharny@gmail.com designates
 74.125.82.178 as permitted sender)
Message-ID: <4E8FED61.5020203@gmail.com>
Date: Sat, 08 Oct 2011 08:27:45 +0200
From: Emmanuel Lecharny <elecharny@gmail.com>
Reply-To: elecharny@apache.org
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6;
 rv:6.0.2) Gecko/20110902 Thunderbird/6.0.2
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: RDN index, oneLevel and sublevel index merge
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Hi guys,

Stefan started to modify the code to get rid of the oneLevel and 
subLevel index, which are more or less useless as we already have the 
hierarchy stored into the rdn index.

However, this rdn index is not good enough as is to be use as a 
replacement for the two other indexes. Its structure forbid us to easily 
retrieve the children from a known entry.

The current RDN index structure is :
<parentId, RDN> -> Entry ID

The key is a tuple containing the parent ID to be able to rebuild the DN.

The reverse index is :
Entry ID -> <parentId, RDN>

We don't have duplicated values.

Now, when we have an entry ID, there is no simple way to get the list of 
all the children for this entry.

We will have to add a third index to deal with such searches :
ParentId -> <entryId, ....>

which will list all the children of a specific entry.

I'm going to investigate around this idea i the next few days.

Thoughts ?

-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com