Re: addIndexesNoOptimize

2009-07-06 Thread Jason Rutherglen
> MergePolicy expects to receive SegmentInfo instances I ran into this implementing LUCENE-1589. On Mon, Jul 6, 2009 at 3:18 AM, Michael McCandless < luc...@mikemccandless.com> wrote: > On Mon, Jul 6, 2009 at 2:18 AM, John Wang wrote: > > > Currently, addIndexesNoOptimize(Directory[] dir) is

Re: addIndexesNoOptimize

2009-07-06 Thread Michael McCandless
On Mon, Jul 6, 2009 at 2:18 AM, John Wang wrote: > Currently, addIndexesNoOptimize(Directory[] dir) is really really > really fast! (I duplicated my index of 15k docs 200 times and created a 3M > doc index in less than a minute) Perhaps we should handle duplicate > directory names more gracef

Re: addIndexesNoOptimize

2009-07-05 Thread John Wang
Hi Mark and Michael: Thanks for your replies. Currently, addIndexesNoOptimize(Directory[] dir) is really really really fast! (I duplicated my index of 15k docs 200 times and created a 3M doc index in less than a minute) Perhaps we should handle duplicate directory names more gracefully?

Re: addIndexesNoOptimize

2009-07-05 Thread Michael McCandless
This was added defensively a while back (can't find the issue right now), because internally IndexWriter now identifies each SegmentInfo as its Directory + segment name. EG the "runningMerges" set makes use of this. If you comment the check out, and pass duplicate segments in, I think at least In