>>Are you closing or committing your IndexWriter after each added
document? Because if you add 100 docs you should not see 100 versions
of these files, only one set of files in the end (many docs are
written to one segment).
No. What I meant to say here is if 100 users have updated the document
It is by design, and 2.4 works the same way.
Are you closing or committing your IndexWriter after each added
document? Because if you add 100 docs you should not see 100 versions
of these files, only one set of files in the end (many docs are
written to one segment).
Each segment holds the docum
Is it by design. The older API (2.4) does not have this problem. Lets say if
I have 100 updates or so.. then it will create 100 versions of those files
in the index. This would increase the number of files in the index directory
and might run into some file issues?
It would be good to just have th
Then those files are expected.
Your 2nd open was with APPEND, which means newly indexed documents are
written into a new set of files.
Lucene is segment based, so your first batch of documents are in
segment _0, while your second batch is in _1 and _2.
Mike McCandless
http://blog.mikemccandless
It's _0.si ( typo)
For second update, create = "false".
Thanks,
Sai.
--
View this message in context:
http://lucene.472066.n3.nabble.com/IndexWriterConfig-OpenMode-CREATE-vs-OpenMode-APPEND-index-files-tp4037766p4037785.html
Sent from the Lucene - Java Users mailing list archive at Nabble.com
I don't know what _0.csi is ... was that supposed to be _0.si?
Did you pass create=true or false for the 2nd update?
Mike McCandless
http://blog.mikemccandless.com
On Thu, Jan 31, 2013 at 1:39 PM, saisantoshi wrote:
> I am using the following below for creating the IndexWriter (for my
> indexi
