Drop support for JDK 14

[dblock]

Is your feature request related to a problem?

In OpenSearch 1.3.0 we stopped testing the complete distribution with JDK 15 in favor of 11, so we can't make claims on compatibility with JDK 15. Plugins never built with JDK15 individually.

The easiest thing to do is probably to just re-add JDK15 to CI matrices so that we can reclaim this compatibility.

But we could also drop JDK 14.

What solution would you like?

Re-add JDK15 to the CI matrix.

or

Remove JDK14 from the CI matrix.

Update: we decided to drop support for JDK 14

• Drop support for JDK 14. alerting#374
• Drop support for JDK 14. anomaly-detection#479
• Drop support for JDK 14. asynchronous-search#121
• Drop support for JDK 14. common-utils#147
• Drop support for JDK 14. reporting#326
• Drop support for JDK 14. index-management#317
• Drop support for JDK 14. job-scheduler#158
• Drop support for JDK 14. k-NN#342
• Drop support for JDK 14. performance-analyzer#174
• Drop support for JDK 14. performance-analyzer-rca#151
• Drop support for JDK 14. security#1718
• Drop support for JDK 14. sql#522
• Drop support for JDK 14. observability#615
• Drop support for JDK 14. cross-cluster-replication#346

[dblock]

@dlvenable Want to comment on whether we should be dropping 14 instead of adding 15?

[dlvenable]

Why would anybody run against either JDK 14 or 15? The only reason I can is that these were (until recently) the "official" versions of OpenSearch. So some users may have decided to run on these JDKs and may have installed them on their clusters.

I suggest that starting in 2.0, OpenSearch only claims compatibility with LTS versions (11 and 17 presently).

It would be valuable to run tests against the latest version of non-LTS Java in order to catch issues which may arise. It could be nice to know that OpenSearch stops working with, say JDK 19.

[peternied]

From a resourcing perspective, I vote for Remove JDK14 from the CI

[dlvenable]

I agree with the vote Remove JDK14 from the CI matrix..

There may be value to keeping it in 1.x since it has been supported in OpenSearch 1.x. But I certainly think there is no reason to test 14 or 15 in 2.x.

[vamsi-amazon]

I agree with vote Remove JDK14 from the CI matrix. Similar to the lines of Java, Opensearch should be compatible with LTS versions JDK11 and JDK17.

[ylwu-amzn]

I think we should keep in 1.x for better backward compatibility. We can remove JDK14 from 2.0 as big version can tolerate some breaking change.

[peternied]

Its been a week now, I do not see any opinions suggesting that we add support for JDK15, making this a once sided issue. @dblock was there any other channels you wanted to get feedback from before we make a decision?

[dblock]

I'd like public comment, but I am waiting on opensearch-project/project-website#670 to be published to ask.

[reta]

+1 to Remove JDK14 from the CI matrix.

[dblock]

Looks like no votes for keeping JDK14. I'm updating the issue and creating sub-issues in projects.