+1, I think the main thing to watch out for is project panama. If we get a 18.x/19.x release with non-incubating APIs, I think it makes sense to create a new major Lucene version. Even if it isn't an OpenJDK LTS release. It could really change a lot, especially regarding hotspots in the code such as postings/dv compression. So it would be great to allow a lot of folks to make a "take two" on these algorithms with vectorization in mind. This is just my opinion.
On Mon, Sep 13, 2021 at 2:10 PM Uwe Schindler <[email protected]> wrote: > > There are no good reasons to do Java 17 and it is way too early. > > > > Reagrding real optimizations, Lucene 17 is unfortunately not containing > Project Panama or Vector API, so it looks more like Java 18/19 is a good > candidate as a new minimum at a later stage. > > > > I’d release Lucene 9 with Java 11 (which is LTS) and then decide later if we > update to some post-17 version to get the new vector and panama APIs (vector > search, SIMD and also MMapDirectory v2). If we do this, we should simply > release Lucene 10. > > > > Uwe > > > > ----- > > Uwe Schindler > > Achterdiek 19, D-28357 Bremen > > https://www.thetaphi.de > > eMail: [email protected] > > > > From: Mike Drob <[email protected]> > Sent: Monday, September 13, 2021 8:00 PM > To: Solr/Lucene Dev <[email protected]> > Subject: Java 11/17 Version Matrix > > > > Hi Devs, > > > > What are our thoughts on Java 11 and 17 version compatibility going forward > for Lucene 9? Will we support both? If so, would Java 11 support likely > continue for the entire 9.x release line? > > > > Is there a JIRA tracking this? > > > > Thanks, > > Mike --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
