lucene-dev mailing list archives

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


Steven Rowe commented on LUCENE-4276:

I agree with Mike M. on all three points:

+1 to put a barrier up for running on JVMs that blatantly cause corruption. This (early, hard
failure) is a service to our users, else they will waste time trying to figure out what's
going on.

+1 to scarily-named user override. -Dlucene.allow.index.corruption seems good.

I don't think we need a separate file ... I think that's over designing it.
> 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, 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