Re: Help! - Max Segment name reached

2018-04-21 Thread Michael McCandless
SENDER BY REPLY EMAIL AND PLEASE DELETE THIS > E-MAIL FROM YOUR SYSTEM AND DESTROY ANY COPIES. > > -Original Message- > From: Uwe Schindler <u...@thetaphi.de> > Sent: Tuesday, April 17, 2018 4:02 PM > To: java-user@lucene.apache.org > Subject: Re: Help! - Max Seg

RE: Help! - Max Segment name reached

2018-04-17 Thread Stuart Goldberg
a-user@lucene.apache.org Subject: Re: Help! - Max Segment name reached Hi, Create a new empty index in a new directory and use addIndex() using the other directory with the broken index. This will copy all segments but renumber them. Uwe Am April 17, 2018 3:52:27 PM UTC schrieb Stuart Goldberg &

Re: Help! - Max Segment name reached

2018-04-17 Thread Uwe Schindler
Hi, Create a new empty index in a new directory and use addIndex() using the other directory with the broken index. This will copy all segments but renumber them. Uwe Am April 17, 2018 3:52:27 PM UTC schrieb Stuart Goldberg : >We have an index that has run into this

Help! - Max Segment name reached

2018-04-17 Thread Stuart Goldberg
We have an index that has run into this bug: https://issues.apache.org/jira/browse/LUCENE-7999 Although this is reported to be fixed in Lucene 7.2, we are at 4.10.4 and cannot upgrade. By looking at the code it seems that the last segment number counter is persisted in segment_h. When