lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicola Buso <nb...@ebi.ac.uk>
Subject MultiReader docid reliability
Date Thu, 29 May 2014 13:29:18 GMT
Hi,

from the javadocs:

----
For efficiency, in this API documents are often referred to via document
numbers, non-negative integers which each name a unique document in the
index. These document numbers are ephemeral -- they may change as
documents are added to and deleted from an index. Clients should thus
not rely on a given document having the same number between sessions. 
----

What does it mean in this context "sessions"? Are search sessions?

1) If I have an index that does not change (no deletes or updates) and
I'm keeping the MultiReader open, can the docid change executing more
times the same search on that reader?

2) Opening the same set of indexes in a MultiReader on different
machines will assign different docids to the same document at runtime or
the algorithm to calculate such docids in some way can guarantee that
static indexes will have the same docids in different machines (than
separated JVMs)?


nicola.



-- 
Nicola Buso <nbuso@ebi.ac.uk>
EMBL-EBI


---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org


Mime
View raw message