Re: Reviving a dead index

Aleksander M. Stensby wrote: > works like a charm Michael! (only thing is that SegmentInfos / > SegmentInfo are final classe, (which I didnt know) so i was bugging > around to really find the classes:) heh. > > I was able to remove the broken segment. I must now get the MAX(id) from > the clean r

Re: Reviving a dead index

One last thing... can i be sure that the latest inserted documents in fact was inserted into that broken segment? Or are they placed randomly in the different segments? - Aleks On Thu, 23 Nov 2006 12:39:19 +0100, Michael McCandless <[EMAIL PROTECTED]> wrote: Aleksander M. Stensby wrote:

Re: Reviving a dead index

works like a charm Michael! (only thing is that SegmentInfos / SegmentInfo are final classe, (which I didnt know) so i was bugging around to really find the classes:) heh. I was able to remove the broken segment. I must now get the MAX(id) from the clean remaining segments, then just regene

Re: Reviving a dead index

Aleksander M. Stensby wrote: Hey, saw this old thread, and was just wondering if any of you solved the problem? Same has happened to me now. Couldn't really trace back to the origin of the problem, but the segments file references a segment that is obviously corrupt/not complete... I thought

Re: Reviving a dead index

Hey, saw this old thread, and was just wondering if any of you solved the problem? Same has happened to me now. Couldn't really trace back to the origin of the problem, but the segments file references a segment that is obviously corrupt/not complete... I thought i might remove the uncomple

Re: Reviving a dead index

Stanislav Jordanov wrote: For a moment I wondered what exactly do you mean by "compound file"? Then I read http://lucene.apache.org/java/docs/fileformats.html and got the idea. I do not have access to that specific machine that all this is happening at. It is a 80x86 machine running Win 2003

Re: Reviving a dead index

Stanislav Jordanov wrote: After all, the Lucene's CFS format is abstraction over the OS's native FS and the App should not be trying to open a native FS file named *.fnm when it is supposed to open the corresponding *.cfs file and "manually" extract the *.fnm file from it. Right? Yes, good c

Re: Reviving a dead index

I missed something that may be very important: I find it really strange, that the exception log reads: java.io.FileNotFoundException: F:\Indexes\index1\_16f6.fnm (The system cannot find the file specified) at java.io.RandomAccessFile.open(Native Method)

Re: Reviving a dead index

Michael McCandless wrote: /This means the segments files is referencing a segment named _1j8s and in trying to load that segment, the first thing Lucene does is load the "field infos" (_1j8s.fnm). It tries to do so from a compound file (if you have it turned on & it exists), else from the fi

Re: Reviving a dead index

Stanislav Jordanov wrote: What might be the possible reason for an IndexReader failing to open properly, because it can not find a .fnm file that is expected to be there: This means the segments files is referencing a segment named _1j8s and in trying to load that segment, the first thing Luc

Reviving a dead index

What might be the possible reason for an IndexReader failing to open properly, because it can not find a .fnm file that is expected to be there: java.io.FileNotFoundException: E:\index4\_1j8s.fnm (The system cannot find the file specified) at java.io.RandomAccessFile.open(Native Method)