[
https://issues.apache.org/jira/browse/SOLR-17205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17829235#comment-17829235
]
Jan Høydahl edited comment on SOLR-17205 at 3/20/24 4:20 PM:
-------------------------------------------------------------
How is that if a user runs her application in JRE21, and imports SolrJ which is
compiled with target Java 11. Will not then the HttpClient from JRE21 be used,
including performance and bug fixes? Our solrj jar does not contain a JRE11
version of HttpClient. But since our source needs to use Java language level 11
in SolrJ, we might not be able to take advantage of AutoClosable until we bump
source-compatibility to a version that supports it, which means a bit more
boilerplate code to close resources. If my assumptions are correct, I see no
downside of only providing JRE11 jars for solrj.
was (Author: janhoy):
How is that if a user runs her application in JRE21, and imports SolrJ which is
compiled with target Java 11. Will not then the HttpClient from JRE21 be used,
including performance and bug fixes? Our solrj jar does not contain a JRE11
version of HttpClient. But since our source needs to use Java language level 11
in SolrJ, we might not be able to take advantage of AutoClosable until we bump
source-compatibility to a version that supports it. If my assumptions are
correct, I see no downside of only providing JRE11 jars for solrj.
> De-couple SolrJ required Java version from server Java version (main)
> ---------------------------------------------------------------------
>
> Key: SOLR-17205
> URL: https://issues.apache.org/jira/browse/SOLR-17205
> Project: Solr
> Issue Type: Task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrJ
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Solr 9.x requires Java 11, both for server and solrj client.
> In Solr 10 we will likely bump required java version to Java 17, or maybe
> even 21, and since we are a standalone app we can do that - on the
> server-side.
> However, to give SolrJ client a broadest possible compatibility with customer
> application environments, we should consider de-coupling SolrJ's java
> requirement from the server-side. That would allow us to be progressive on
> the server side Java without forcing users to stay on latest Java in their
> apps.
> I don't know if it makes much sense to be compatible too far back on EOL java
> versions, but perhaps let SolrJ stay one LTS version behind the server for
> broad compatibility.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
