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 (athena.apache.org: domain of elecharny@gmail.com
 designates 72.14.220.159 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=sender:message-id:date:from:user-agent:mime-version:to:subject
         :references:in-reply-to:content-type:content-transfer-encoding;
        b=ONA93+24VPtxFEcQXfW0zHEKxysEbfdVTPPLrE5GmWrFFxCdsEQ3I98fFQ1DO+ZJC2
         vpcWtIPdW7icrjm29gdpBqDW96opF4fD1YOfs0tKB+kVArm43Dgsisv9rp8aWttWk69G
         LdG5vQ0chazA56KiXxrqEGo6vgcP3PAN0FNiI=
Sender: Emmanuel Lecharny <elecharny@gmail.com>
Message-ID: <4A0D1A0F.30304@nextury.com>
Date: Fri, 15 May 2009 09:30:23 +0200
From: Emmanuel Lecharny <elecharny@apache.org>
User-Agent: Thunderbird 2.0.0.21 (X11/20090318)
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: [index review] Index rebuilding/creation
References: <4A0BE9EC.5080707@nextury.com>
	 <a32f6b020905141332qa76cbedpc3b8f25533ca7623@mail.gmail.com>
	 <4A0C96E7.6070703@nextury.com>
 <a32f6b020905141559x126e082fm9547e3c89e278373@mail.gmail.com>
 <4A0CA9E8.7070008@nextury.com> <4A0CF166.1040809@gmail.com>
In-Reply-To: <4A0CF166.1040809@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

I have renamed the thread, because I think we need to discuss everything 
about index construction or reconstruction when the server already 
contains data.

Kiran Ayyagari wrote:
>
>
> Emmanuel Lecharny wrote:
>> Ok, let's go deep into each system index now. We don't really care 
>> about user index right now.
>>
>> First, we have to know that a system index can still be configured in 
>> the Server.xml file, because the user can set the index size. We need 
>> to clarify exactly what can be configured, what is the default and 
>> also discuss about what can be improved.
>>
>> 1) What can be configured
>>
>> Let's list the parameter we can work on :
>> - wkDirPath : the working directory path used to store the index
>
> <paranoia>
>  What if the user configures it to '/tmp' and reboots the machine 
> after the server has loaded some data.
>  All the indexed data would be lost. May be we should warn users about 
> it in the doc
> </paranoia>
We can't protect users against themselves... Someone deciding to put an 
index on /tmp either knows what he does or deserves to see his index 
being deleted on reboot ;)

>
> We should have some mechanism where by the server notifies the user 
> either to rebuild the index or
> the server itself does it.
I was thinking about the index rebuilding problem, or more probably, 
index building after addition of one index after data has been injected 
into the server. We need such a tool, the thing is how to implement it ? 
Is it possible to have a on-line index construction system ? (ie, a 
mechanism able to build an index while the server is running).

IMHO, I think we should offer a simple index creation system. It can be 
activated as a separate process, or probably better, as a startup option 
for the server, so we can invoke it through Studio.
>
> This should be easy as we already have a command line tool to rebuild 
> the index the only thing is to fix
> this partially broken tool (I have started to fix this tool sometime 
> back but it hasn't come out of
> workspace may be for 2.0 it will :) and add some code to the server to 
> notify the user.
That could be a good start.


-- 
--
cordialement, regards,
Emmanuel L�charny
www.iktek.com
directory.apache.org