On Sat, May 12, 2012 at 9:12 AM, Valeriy Felberg
wrote:
>> the Document IDs in Lucene are per segment. ie. they are always
>> segment based.
>
> @Simon I'm just wondering: If the document IDs are per segment how
> does it work if I call Searcher.search(Query, int) and get TopDocs
> referencing Sco
> the Document IDs in Lucene are per segment. ie. they are always
> segment based.
@Simon I'm just wondering: If the document IDs are per segment how
does it work if I call Searcher.search(Query, int) and get TopDocs
referencing ScoreDocs which contain document IDs? What happens if
there are two m
On Fri, May 11, 2012 at 7:56 AM, Jong Kim wrote:
> When I update a document in Lucene (i.e., re-indexing), I have to delete
> the existing document, and create a new one. My understanding is that this
> assigns a new doc ID for the newly created document. If that is the case,
> is it true that the
On Fri, May 11, 2012 at 9:56 PM, Jong Kim wrote:
> 2. If Lucene can recycle old IDs, it would be even better if I could force
> it to re-use a particular doc ID when updating a document by deleting old
> one and creating new one. This scheme will allow me to reference this doc
> ID from another do
When I update a document in Lucene (i.e., re-indexing), I have to delete
the existing document, and create a new one. My understanding is that this
assigns a new doc ID for the newly created document. If that is the case,
is it true that the system can rather quickly run out of doc ID space
(which
