What is the problem with implementing the KinoSearch model for
Lucene? It seems this would solve nearly all of these issues in a
very srtaightfoward way.
BTW, the KinoSearch model is nearly exactly what we did when we our
original implementation of IndexReader/Writer wrote directly to JDBC.
It would seem that a very simple SortPool implementation that did
everything in memory would be ideal for Lucene server based
environments.
On Jan 16, 2007, at 4:18 PM, Marvin Humphrey wrote:
Late response...
On Jan 12, 2007, at 3:02 AM, Michael McCandless wrote:
Now that readers are read-only, I think it makes sense to default the
write lock into the index directory, and as you describe, no longer
generate a "unique namespace" hash lock ID since the index dir gives
us that scoping.
For the record, it was Doug who originally pointed out that we no
longer needed the lock dir.
Well, I look forward to seeing whether you can suggest
improvements on some of the algos I'll bring up in this forum
once KS 0.20_01 is out. :)
I will try, but I'm already behind just trying to understand how we
could improve Lucene based on your current KS release! Is there any
preview/general summary of what's being done for KS 2.0/Lucy?
There isn't a general summary. KS 0.20 moves away from Lucene in
several ways. It's a bit of an experiment, and while a lot of it
will end up in Lucy, the more significant changes we'll just have
to see about. Since I'm blessed and cursed as the sole coder on
KS, it's easier for me to JFDI and then present a fully documented,
tested, benchmarked, coherent codebase than to present something
half-baked and explain all the missing pieces.
The main item from the current release is the KinoSearch merge
model. There's a high-level description of the algorithm on the
Lucy wiki: <http://wiki.apache.org/lucy/KinoSearchMergeModel>.
Marvin Humphrey
Rectangular Research
http://www.rectangular.com/
---------------------------------------------------------------------
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]
