As long as you are really sure it's not corrupt (by running
CheckIndex) then you do not need to rebuild it.
Mike
dan at gmail wrote:
Mike,
I have one more question.
I have another set of index data which were built with Lucene 2.3.2
and JRE
1.6.0_06 and this set index has not been corrupted yet. If I
downgrade to
JRE 1.6.0_03, do I need to rebuild this index with JRE 1.6.0_03 or I
can
continue to use this index with 1.6.0_03?
Thanks,
Dan
Michael McCandless-2 wrote:
Yes, downgrading is really the only option now, unfortunately.
That, and voting for this bug at Sun (note you can vote for the same
bug 3 times), which seems to be the root cause of the corruption:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6707044
It's been open for 6 weeks now and besides being accepted by Sun
there's been no other response. It's marked (surprisingly) as low
priority.
While we've worked around it in Lucene, as best I can tell, you
really
can't be sure so downgrading is the safest course of action.
Mike
dan at gmail wrote:
Hello,
I don't have a good understanding of what options for avoid this
corrupted
index problem described in LUCENE-1282. It seems to me that I
either
downgrade JRE from 1.6.0_06 to 1.6.0_03, or wait for an official
release of
Lucene 2.4.0 which includes a workaround for this JRE bug.
http://issues.apache.org/jira/browse/LUCENE-1282
Do I have any other options?
Thanks,
Dan
--
View this message in context:
http://www.nabble.com/LUCENE-1282-tp18224180p18224180.html
Sent from the Lucene - Java Users mailing list archive at
Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/LUCENE-1282-tp18224180p18228381.html
Sent from the Lucene - Java Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
