lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <>
Subject [jira] Commented: (LUCENE-555) Index Corruption
Date Tue, 25 Apr 2006 18:01:06 GMT
    [ ] 

Doug Cutting commented on LUCENE-555:

Calling folks names probably won't help your agenda.  Running away probably won't help your
agenda either.  What might help it it is calm, polite, persistent engagement.  Lucene is changed
primarily by folks who use Lucene.  Other users are telling you that they don't personally
require this sort of recovery.  Perhaps that's even a self-defining characteristic: if they
needed it then they wouldn't be using Lucene.

So, if you need this in Lucene, the best way to get it added is to help add it.  If you're
not interested in helping, then this will probably have to wait until someone else who needs
it comes along and is willing to make it happen.  So, if you want to help, examine the file
formats document and make a proposal.  Then, if it looks like it might work, contribute a
patch that implements it.  Perhaps you'll be able to identify some collaborators to help out.
 Perhaps not.  That's the way Lucene changes.

> Index Corruption
> ----------------
>          Key: LUCENE-555
>          URL:
>      Project: Lucene - Java
>         Type: Bug

>   Components: Index
>     Versions: 1.9
>  Environment: Linux FC4, Java 1.4.9
>     Reporter: dan
>     Priority: Critical

> Index Corruption
> >>>>>>>>> output
> ../_aki.fnm (No such file or directory)
>         at Method)
>         at<init>(
>         at$Descriptor.<init>(
>         at<init>(
>         at
>         at org.apache.lucene.index.FieldInfos.<init>(
>         at org.apache.lucene.index.SegmentReader.initialize(
>         at org.apache.lucene.index.SegmentReader.get(
>         at org.apache.lucene.index.SegmentReader.get(
>         at org.apache.lucene.index.IndexWriter.mergeSegments(
>         at org.apache.lucene.index.IndexWriter.mergeSegments(
>         at org.apache.lucene.index.IndexWriter.optimize(
> >>>>>>>>> input
> - I open an index, I read, I write, I optimize, and eventually the above happens. The
index is unusable.
> - This has happened to me somewhere between 20 and 30 times now - on indexes of different
shapes and sizes.
> - I don't know the reason. But, the following requirement applies regardless.
> >>>>>>>>> requirement
> - Like all modern database programs, there has to be a way to repair an index. Period.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message