You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "David Smiley (Jira)" <ji...@apache.org> on 2025/11/07 22:05:00 UTC

[jira] [Commented] (SOLR-17161) Separate out a solrj-jetty artifact (10.0)

    [ https://issues.apache.org/jira/browse/SOLR-17161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18036415#comment-18036415 ] 

David Smiley commented on SOLR-17161:
-------------------------------------

h2. This is a big change coming...

I am introducing the following new classes in a new package {{org.apache.solr.solrj.jetty}}:
*HttpJettySolrClient*, +renamed+ from Http2SolrClient
*CloudJettySolrClient*.  New; it +extends+ CloudHttp2SolrClient.  Perhaps what it extends ought to be renamed as CloudBaseSolrClient, albeit it's not terribly named as-is.  CloudHttp2SolrClient becomes abstract.
*LBJettySolrClient*.  It +extends+ LBHttp2SolrClient.  Perhaps what it extends ought to be renamed LBBaseSolrClient, albeit it's not terribly named as-is.

The JDK ones ought to get similar treatment but that can be a separate issue/PR.

> Separate out a solrj-jetty artifact (10.0)
> ------------------------------------------
>
>                 Key: SOLR-17161
>                 URL: https://issues.apache.org/jira/browse/SOLR-17161
>             Project: Solr
>          Issue Type: Sub-task
>          Components: clients - java
>            Reporter: Jan Høydahl
>            Assignee: David Smiley
>            Priority: Blocker
>             Fix For: 10.0
>
>
> Given we have a native JDK based client in SOLR-599, we can separate out all {{Http2SolrClient}} and freiends with their jetty-client dependencies into a separate artifact {{{}solrj-jetty{}}}.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org