Excellent, that's the way to go. I hadn't realized that method was
public.
Mike
Daniel Noll wrote:
Michael McCandless wrote:
You could look at the docID of each hit, and compare to
the .maxDoc() of each underlying reader.
There is also MultiSearcher#subSearcher(int) which also works a
Michael McCandless wrote:
You could look at the docID of each hit, and compare to the .maxDoc() of
each underlying reader.
There is also MultiSearcher#subSearcher(int) which also works as you add
more without having to do the maths yourself.
Daniel
--
Daniel Noll
You could look at the docID of each hit, and compare to the .maxDoc()
of each underlying reader.
MultiSearcher logically "concatenates" the docIDs.
However, docIDs are an internal identifier for Lucene, so it's always
possible in a new release of Lucene that how docIDs are mapped by
Mult
Hello,
i have a short question to the MultiSearcher. Is it possible to identify from
which index a result/hit comes when i use a MultiSearcher (2 Indizes)?
Thank you for your help.
Greets
Oliver
On Friday 01 December 2006 15:16, Kai R. Emde wrote:
> When we search "material" as an example, we found 207 hits in the the
> index. When we search this index in the multisearcher, with 3 index,
> there 206 hits contiguous and one after the next. OK bookA1, bookA2,
> bookA3 ... bookA206, bookB1,
ngliche Nachricht-
Von: Daniel Naber [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 30. November 2006 00:23
An: java-user@lucene.apache.org
Betreff: Re: BUG ? - lucene multisearcher / sorting
On Tuesday 28 November 2006 23:09, Kai R. Emde wrote:
> we have one problem with the sort routine
On Tuesday 28 November 2006 23:09, Kai R. Emde wrote:
> we have one problem with the sort routine. We use the multisearcher
> function over severall index.
Does that also happens when you're not using MultiSearcher? Could you post
a small test case that demonstrates this problem? To my knowledge
Hello,
we have one problem with the sort routine. We use the multisearcher function
over severall index.
The result will be sorted by the booknumber, but the produced list isn't
sorted correct. There are 300 hits from book a, then 150 from book b, 95
hits book 3, but then there are 1,2,3 hits of
