K. Thanks for the clarification.
On Wed, Oct 17, 2012 at 7:10 PM, Ian Lea wrote:
> I guess so. I don't pay much attention to these figures but
> presumably IndexReader.numDocs() and numDeletedDocs() will adjust as
> deletions get merged away. Try it and see.
>
>
> --
> Ian.
>
>
> On Wed, Oct 1
I guess so. I don't pay much attention to these figures but
presumably IndexReader.numDocs() and numDeletedDocs() will adjust as
deletions get merged away. Try it and see.
--
Ian.
On Wed, Oct 17, 2012 at 2:09 PM, Deepak Shakya wrote:
> Oh is it. So whenever in future these segments gets merg
Oh is it. So whenever in future these segments gets merged, i will have my
document count going down right?
On Wed, Oct 17, 2012 at 6:33 PM, Ian Lea wrote:
> Yes, IndexWriter.updateDocument() deletes and then adds. See the
> javadocs. So your index will have deleted docs. Why do you care?
> Th
Yes, IndexWriter.updateDocument() deletes and then adds. See the
javadocs. So your index will have deleted docs. Why do you care?
They'll go away eventually as segments get merged.
If you really do care, see IndexWriter,forceMergeDeletes(). See also
the javadoc for that: This is often a horribl
I am using updateDocument() method to update my document in the lucene
index. Here is how I am doing it.
writer.updateDocument(new Term(Constants.DOC_ID_FIELD,
doc.get(Constants.DOC_ID_FIELD)), doc);
I check my index data with Luke, and find that on second run of the
indexing, Luke tells that Del
