Hi,
Yes, that is all fine. Because the index merging is concurrent, the order of
documents in the resulting index may be different. This is not different than
with relational database systems if you insert tables into others (the order of
rows is also undefined).
About your question: The diffe
right, for docs with the same score, ties are broken by the internal Lucene ID.
This may even change _on the same node_ due to merges!
If you want to control this, consider always specifying a secondary sort by,
say, your id field if you have one, or date stamp or..
Best,
Erick
On Thu, May 2
Hi Uwe,
thanks for the reply.
I see slightly different order in the results, and I was thinking are
docs with the same score and the difference between the two index (one
with "addIndexes" multithreaded and one no) is because of the order of
insert in the merged index; could be this the difference
Hi Nicola,
Yes, it is thread safe, like all other methods in IndexWriter. In the case of
the one taking IndexReaders, Lucene will also do the merging concurrently.
Say hello to Jo McEntyre! :-)
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@theta
Hi,
I was wondering if it's correct to call the method:
IndexWriter.addIndexes(...)
from different threads concurrently.
nicola.
-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mai
I was certainly asking about lucene!
> From: j...@basetechnology.com
> To: java-user@lucene.apache.org
> Subject: Re: Multi-thread indexing, should the commit be called from each
> thread?
> Date: Wed, 21 May 2014 11:53:46 -0400
>
> (Was this supposed to be a java-user/Lucene question or a Solr
