lucene-dev mailing list archives

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


Robert Muir commented on LUCENE-4276:

An external file allows one to add additional versions later on. E.g. we don't know today
that an already released JVM doesn't cause such bugs, because we didn't test it, or it will
appear later on. It's another reason to put this check in a file.

Then, for people that use Lucene to create software for other people, they can add such versions
to the file, instead of recompiling Lucene.

Those people can implement their own checks in their own apps for whatever criteria they want:
I don't think we need to build infrastructure for them to do that.

I just want to have a check against the most ridiculous index corruption bugs (thats why i
suggested this 1.7.0 one only here, I know there are others but in my opinion its the most
dangerous and widespread).

> 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