On 08/06/2005, at 1:33 AM, Paul Elschot wrote:
On Tuesday 07 June 2005 11:42, Matt Quail wrote:
I've been playing around with a custom Query, and I've just realized
that my Scorer is likely to return the same document more then once.
Before I delve a bit further, can anyone tell
I've been playing around with a custom Query, and I've just realized
that my Scorer is likely to return the same document more then once.
Before I delve a bit further, can anyone tell me if this is this a
Bad Thing?
=Matt
We have a system where I'll be given 10 or 20 unique keys.
I assume you mean you have one unique-key field, and you are given
10-20 values to find for this one field?
Internally I'm creating a new Term and then calling
IndexReader.termDocs() on this term. Then if termdocs.next()
matches
I have a similar problem, for which ParallelReader looks like a good
solution -- except for the problem of creating a set of indices with
matching document numbers.
I have wondered about this as well. Are there any *sure fire* ways of
creating (and updating) two indices so that doc numbers in
I have also just seen this exception in a production system (lucene
1.4.3).
Any tips on what might be causing it? I'll be attempting to reproduce
it later, but I'm quite confident that while I'm using that
IndexWriter, no other readers are open, and no other Writers, either.
java.lang.Illeg
