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 13:27:35 GMT


Shai Erera commented on LUCENE-4276:

Sigh. I was hoping to get to consensus here.

As for the patch, if that comes from a file, I'd feel better to support it.

Few separate comments:
# Can we include some text in the message, describing why it's incompatible, such as a link
to a JIRA issue / markmail thread?
# How do you know to recommend a specific build version?
#* Perhaps instead of recommending a version, we should include in the exception all the versions
that are not supported? That way, we only commit to what we tested and is not supported.
#* I'm worried that we'll recommend a version that will later turn out to be broken, and won't
remove the 'recommendation' text.

> 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
> 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