[
https://issues.apache.org/jira/browse/SOLR-12809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16797506#comment-16797506
]
Erick Erickson commented on SOLR-12809:
---------------------------------------
Thinking about this a bit and prompted by David's comments, I think it's
similar conceptually to: [https://wiki.apache.org/lucene-java/JavaBugs.]. What
I'm after here is something we can just point people to saying "this is our
knowledge so far, both from our testing and reports from the field". I agree
that this is different than certifying a version. And consistent with what
we've done in the past to list known issues rather than recommend.
Kind of flipping my matrix idea around. It'd look something like this (this is
not accurate)....
|| ||Solr 5x||Solr 6x||Solr 7x||Solr 8x||Solr 9x||
|Java 7|0|1|1|1|5|
|Java 8|0|0|0, 6|0|5|
|Java 9|4|2, 3|2, 3|2, 3|5|
.
.
.
[0] No known issues
[1] Java 8 is the minimum Java required
[2] No good reason to prefer Java 9 over Java 11.
[3] SOLR-10355, fixed in Java 9 version XYZ (if true)
[4] Not part of Solr/Lucene testing regimens, use at own risk (a little
gentler than that, but...)
[5] Java 11 is the minimum requirement
I don't particularly want to go back and worry about, say, java 9 or 10, it's
fine IMO to just say "use Java 11 instead" if that's our consensus.
Ditto which release of Java 11. If we were to _start_ anything like this with
the most-recent Java 11, that'd be fine.
What I'm looking for here is something we can send users to go give them a
decent idea of what we _know_, especially when they want to use OpenJDK. It
doesn't matter what the relationship between the Oracle and OpenJDK versions
are, we just need to give some guidance.
The Jira could mention any specific versions affected, fixed versions and
whether the source of the Java version mattered. Users are confused if there
are any differences between OpenJDK and Oracle's paid versions, so we could
clarify that too.
How about this. I'll start a Wiki page with all sorts of big, red warnings
about how it's under construction and not complete with lots of TBDs that
people can edit freely until we get it into shape and we'll go from there.
> Document recommended Java/Solr combinations (JDK 11?)
> -----------------------------------------------------
>
> Key: SOLR-12809
> URL: https://issues.apache.org/jira/browse/SOLR-12809
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Erick Erickson
> Assignee: Erick Erickson
> Priority: Major
>
> JDK 8 will be EOL early next year (except for "premier support"). JDK 9, 10
> and 11 all have issues for Solr and Lucene IIUC.
> Also IIUC Oracle will start requiring commercial licenses for 11.
> This Jira is to discuss what we want to do going forward. Among the topics:
> * Skip straight to 11, skipping 9 and 10? If so how to resolve current
> issues?
> * How much emphasis on OpenJDK .vs. Oracle's version
> * What to do about dependencies that don't work (for whatever reason) with
> the version of Java we go with?
> * ???
> This may turn into an umbrella Jira with sub-tasks of course. Since JDK 11
> has had a GA release, I'd also like to have a record of where the current
> issues are to refer people to.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
