Re: SQLDirectory

[Doug Cutting]

That sort of representation works well for a static index, but it's not 
efficient to modify.  One could do this in Lucene by directly 
implementing the IndexReader API against an SQL database.  The database 
tables could be populated from a file-based IndexReader.  But I think 
implementing IndexWriter this way would be very slow.

Doug

Chong, Herb wrote:
there are a couple of people who participated in TREC that used a relational database to directly store the postings list for each term. from what i recall, search performance in terms of elapsed time was reasonable, not particularly fast nor slow. i gather that each term's posting list was an individual BLOB in the database. the term string was used as the index column. i believe the group used stemming.

Herb...

-----Original Message-----
From: Doug Cutting [mailto:[EMAIL PROTECTED]
Sent: Friday, February 06, 2004 4:11 PM
To: Lucene Users List
Subject: Re: SQLDirectory
Also, in some environments, the only supported access to reliable, 
redundant, shared data might be through a database.  An SQLDirectory 
would enable one to deploy a Lucene-based application in such an 
environment without having to, e.g., get permission from operations to 
enable NFS.

Doug

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]