[
https://issues.apache.org/jira/browse/LUCENE-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13425775#comment-13425775
]
Uwe Schindler commented on LUCENE-4276:
---------------------------------------
bq. IMO, we must provide the ability to override. Changing the JVM is not
trivial in some organizations for a variety of reasons, from "policy" to worry
about whether version X is compatible with all the other apps (yeah, I know you
can run multiple JVMs, but we're talking corporate policy here) to only using
certified JVMs. Making this non-overridable would lock Solr/Lucene out of
running in some organizations.
On the other hand if you use this exactly JVM and startup your Solr instance it
may crash when it uses PorterStemmer (OK, that's not bad at all because its
another form of Robert's Runtime Exception - I just point that out: Solr in
default configuration crashes after indexing the example docs, we tried that
out), but if you are working around that by using not PorterStemmer, the worse
thing is: After the first commit on your maybe holy index, it is correup,
really. If you are in such a company, you have no chance to run Solr/Lucene -
then its also fine to fail early, the override would be useless.
If you are in such a company that forces you to use JDK 1.7.0b147 (also known
as 1.7.0GA), then they also won't allow you to pass -XX:-UseLoopPredicate. So
at the end you cannot run Solr at all, so why not fail early instaed of late
when people complain at your Consulting Company.
In general we should have a list of failing JDKs in the release notes. We
started to do this in Lucene/Solr 3.5.0 where we "oficially declared Lucene as
Java 7 compatible" with explicitely stating that "you have to use u1 or later".
> 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: [email protected]
For additional commands, e-mail: [email protected]
