lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-4276) refuse to execute on broken corrupting jvms
Date Tue, 31 Jul 2012 13:53:35 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13425774#comment-13425774
] 

Robert Muir commented on LUCENE-4276:
-------------------------------------

{quote}
No, we still need an override. We do not always know best.
{quote}

What does this mean? if you don't supply this option, loops are broken and it creates corrupt
indexes.

Why is it so important we have our own override that *allows* someone to create a corrupt
index?
Why can't the override be the workaround that also prevents corruption?
                
> refuse to execute on broken corrupting jvms
> -------------------------------------------
>
>                 Key: LUCENE-4276
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4276
>             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 Constants.java 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message