[
https://issues.apache.org/jira/browse/LUCENE-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13425708#comment-13425708
]
Shai Erera commented on LUCENE-4276:
------------------------------------
bq. Creating corrupt index is NOT A USE CASE
Depends :). If the corrupt index is a result of using DirectPF Codec, or using
payloads etc., then it is a use case. If the corrupt index is a result of
adding one field with one word, untokenized and all, then that's a more serious
corruption, and how we handle/inform it should be discussed.
At any rate, I've seen apps preventing to run on old JVMs, but not future,
potentially buggy, JVMs. What if we'll detect a corruption related to a certain
Linux kernel version - would we prevent Lucene from running there too?
> 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
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
