lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shai Erera (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4276) refuse to execute on broken corrupting jvms
Date Tue, 31 Jul 2012 14:23:34 GMT


Shai Erera commented on LUCENE-4276:

Can you add to the message "This JVM is incompatible with Lucene, and may/will lead to index
corruption"? It's more informative.

And, can you please describe here what's leading to the corruption? I.e. if I do:
* new IndexWriter().close()
* new IndexWriter().forceMerge()/maybeMerge().close()
* new IndexWriter().addDocument().commit().close()
Will all of these lead to corruption? Only some of them? What class causes the corruption,
due to the bug?
> refuse to execute on broken corrupting jvms
> -------------------------------------------
>                 Key: LUCENE-4276
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Task
>            Reporter: Robert Muir
>            Priority: Blocker
>             Fix For: 4.0
>         Attachments: LUCENE-4276.patch, LUCENE-4276.patch
> There are some jvms where we know lucene does not work at all and will just produce things
like corrupt indexes.
> We should detect this in a static block of and refuse to run at all.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


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

View raw message