RE: Restoring a corrupt index

2004-08-19 Thread Honey George
ilto:[EMAIL PROTECTED] > Sent: Thursday, August 19, 2004 2:08 PM > To: Lucene Users List > Subject: RE: Restoring a corrupt index > > > This is what I did. > > There are 2 classes in the lucene source which are > not > public and therefore cannot be accessed from

RE: Restoring a corrupt index

2004-08-19 Thread Karthik N S
Hi George Do u think ,the same would work for MERGED Indexes Please Can u suggest a solution. Karthik -Original Message- From: Honey George [mailto:[EMAIL PROTECTED] Sent: Thursday, August 19, 2004 2:08 PM To: Lucene Users List Subject: RE: Restoring a corrupt index

RE: Restoring a corrupt index

2004-08-19 Thread Honey George
NDEX, Categorized accordingly. > > There may be a possibility of Corruption, So > Please do post the code > reffrals > > > Thx > Karthik > > > -Original Message- > From: Honey George [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 18,

RE: Restoring a corrupt index

2004-08-18 Thread Karthik N S
rals Thx Karthik -Original Message- From: Honey George [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 18, 2004 5:51 PM To: Lucene Users List Subject: Re: Restoring a corrupt index Thanks Erik, that worked. I was able to remove the corrupt index and now it looks like the index i

Re: Restoring a corrupt index

2004-08-18 Thread Honey George
Thanks Erik, that worked. I was able to remove the corrupt index and now it looks like the index is OK. I was able to view the number of documents in the index. Before that I was getting the error, java.io.IOException: read past EOF I am yet to find out how my index got corrupted. There is another

Re: Restoring a corrupt index

2004-08-18 Thread Erik Hatcher
, August 17, 2004 10:35 AM To: Lucene Users List Subject: RE: Restoring a corrupt index Wallen, Which hex editor have you used. I am also facing a similar problem. I tried to use KHexEdit and it doesn't seem to help. I am attaching with this email my segments file. I think only the segment with

RE: Restoring a corrupt index

2004-08-18 Thread Honey George
PROTECTED] wrote: > http://www.ultraedit.com/ is the best! > > However, I cannot imagine how another hexeditor > wouldnt work. > > -Original Message- > From: Honey George [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 17, 2004 10:35 AM > To: Lucene Users List

[OT] Re: Restoring a corrupt index

2004-08-17 Thread Patrick Burleson
raedit.com/ is the best! > > However, I cannot imagine how another hexeditor wouldnt work. > > > > -Original Message- > From: Honey George [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 17, 2004 10:35 AM > To: Lucene Users List > Subject: RE: Restor

RE: Restoring a corrupt index

2004-08-17 Thread wallen
List Subject: RE: Restoring a corrupt index I think attachments are filtered. This is what I see when I open in the hex editor. : 00 04 e0 af 00 00 00 02 05 5f 36 75 6e 67 00 04 ..à¯._6ung.. :0010 1e fb 05 5f 36 75 6e 69 00 00 00 01 00 00 00 00 .û._6uni :0020 00 00 c1 b4

RE: Restoring a corrupt index

2004-08-17 Thread wallen
http://www.ultraedit.com/ is the best! However, I cannot imagine how another hexeditor wouldnt work. -Original Message- From: Honey George [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 17, 2004 10:35 AM To: Lucene Users List Subject: RE: Restoring a corrupt index Wallen, Which hex

RE: Restoring a corrupt index

2004-08-17 Thread Honey George
I think attachments are filtered. This is what I see when I open in the hex editor. : 00 04 e0 af 00 00 00 02 05 5f 36 75 6e 67 00 04 ..à¯._6ung.. :0010 1e fb 05 5f 36 75 6e 69 00 00 00 01 00 00 00 00 .û._6uni :0020 00 00 c1 b4 ..Á´

RE: Restoring a corrupt index

2004-08-17 Thread Honey George
Wallen, Which hex editor have you used. I am also facing a similar problem. I tried to use KHexEdit and it doesn't seem to help. I am attaching with this email my segments file. I think only the segment with name _ung is a valid one, I wanted to delete the remaining..but couldn't. Can you help? -G

RE: Restoring a corrupt index

2004-08-16 Thread wallen
I fixed my own problem, but hope this might help someone else in the future: I went into my segments file (with a hex editor), deleted the record for _cu0v and changed the length 0x20 to be 0x1f, and it seems I have most of my index back! Maybe a developer could elaborate on this? -Original