Let's wait for this functionality and see what happens. If the gain is
significant then this provides an incentive to upgrade for everyone.
MR-JARs will be a pain to keep consistent...
Dawid
On Tue, Sep 14, 2021 at 10:19 AM Adrien Grand wrote:
> I think we should discuss options when Project Pa
Sorry, this is a bogus argument. Nobody is holding a gun to anyone's
head and forcing them to upgrade.
When we have new major functionality, we should be able to issue new
major releases, to hell with elasticsearch users.
On Tue, Sep 14, 2021 at 4:19 AM Adrien Grand wrote:
>
> I think we should
I think we should discuss options when Project Panama is released. Doing
frequent major releases forces users to reindex more often. If Project
Panama was released shortly and we decided to release Lucene 10
immediately, this would force users to reindex their 8.x data to be able to
upgrade, I know
In addition: we test for compatibility with Java 17 (both Lucene and Solr), so
consumer is still able to use any version and has enough flexibility.
Uwe
Am 13. September 2021 18:52:53 UTC schrieb Dawid Weiss :
>I agree with Uwe and Robert. JDK11, then the min bar should move if there
>is somethi
I agree with Uwe and Robert. JDK11, then the min bar should move if there
is something that brings value (be it performance, LTS or some other
attractive option).
Dawid
On Mon, Sep 13, 2021 at 8:15 PM Robert Muir wrote:
> +1, I think the main thing to watch out for is project panama. If we
> ge
+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 a
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
hat HTTP version randomly to support".
>
> Uwe
>
> -
> Uwe Schindler
> Achterdiek 19, D-28357 Bremen
> http://www.thetaphi.de
> eMail: [email protected]
>
> > -Original Message-
> > From: Erick Erickson
> > Sent: Wednesday, December 12, 2018 1:45 AM
>
Uwe
-
Uwe Schindler
Achterdiek 19, D-28357 Bremen
http://www.thetaphi.de
eMail: [email protected]
> -Original Message-
> From: Erick Erickson
> Sent: Wednesday, December 12, 2018 1:45 AM
> To: [email protected]
> Subject: Re: Java 11.
>
> Well, you've
Well, you've done a lot more thorough testing of the different
versions of Java than I have. I regularly see many more tests failing
that have JDK11 in the title, but perhaps it's all the TLS stuff.
bq. ...think, if you want to use SSL/TLS, the status in Java 11 is undefined
This is a pretty imp
Hi Erick,
> I just noticed that Solr's CHANGES.txt has this at the beginning:
>
> You need a Java 1.8 VM or later installed.
>
> Is this still what we want to say between now and whenever we
> understand the various failures on jdk 9, 10, 11 and 12? Do we want to
> specifically say that 9 and 10
11 matches
Mail list logo
