An option: instead of merging continuously as you run, you can optimize with
'maxSegments=10'. This mean 'optimize but only until there are 10 segments'. If
there are fewer than 10 segments, nothing happens. This lets you schedule
merging I/O.
Is the number of files a problem due to file space
Scott, did you mean the Lucene integer id, or the unique id field?
- Original Message -
| From: "Martijn v Groningen"
| To: java-user@lucene.apache.org
| Sent: Sunday, October 28, 2012 2:24:29 PM
| Subject: Re: Lucene 4.0 delete by ID
|
| A top level document ID can change over time. For
A top level document ID can change over time. For that reason you
shouldn't rely on it. However if you know your index is stable or you
keep track when a merge happes, you can use the
IndexWriter#tryDeleteDocument method to delete a document by Lucene
id. Deleting a document via a IndexReader is no