Mailing-List: contact lucene-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Lucene Users List" <lucene-user@jakarta.apache.org>
Mime-Version: 1.0
Message-Id: <p05200f00ba9e4c8e2a94@[10.1.4.99]>
Date: Wed, 19 Mar 2003 11:43:26 -0500
To: Lucene Users List <lucene-user@jakarta.apache.org>
From: Avi Drissman <avi_drissman@baseview.com>
Subject: Putting the Lucene index into a database
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

I've successfully used Lucene to do indexing of about 50-100K files, 
and have been keeping the index on a local disk. It's time to move 
up, and now I'm planning to index from 100-500K files.

I'm trying to decide whether or not it pays to hold the index in our 
database. Our database (FrontBase) has decent blob support, and a 
~300 meg index likely wouldn't faze it, but I have some concerns.

First, I'm looking at Directory, and there are two functions:
* OutputStream createFile(String name)
* InputStream openFile(String name)

How much of the streams do they take advantage of? Does Lucene seek 
around? I'm concerned about huge re-writing of files.

Second is speed. I was looking at SQLDirectory, and although I'd 
probably write my own (inspired by that), who's using it? How is the 
speed compared to flat-files?

Third is replication. We're aiming for a replicated environment. If 
we wanted to build the index on the disk rather than in the database, 
every server would have to keep their own copy. Does anyone have any 
experience in this?

Thanks.

Avi

-- 
Avi 'rlwimi' Drissman
avi@baseview.com
Argh! This darn mail server is trunca

---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org