[
https://issues.apache.org/jira/browse/SOLR-15223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17432445#comment-17432445
]
Jan Høydahl commented on SOLR-15223:
------------------------------------
I think I found answer to my last question, JDK http client does not support
several authentication schemes or multi-part etc
(https://www.mocklab.io/blog/which-java-http-client-should-i-use-in-2020/#the-clients)
> Deprecate HttpSolrClient, mark httpcomponents dep as "optional" in SolrJ
> ------------------------------------------------------------------------
>
> Key: SOLR-15223
> URL: https://issues.apache.org/jira/browse/SOLR-15223
> Project: Solr
> Issue Type: Improvement
> Components: SolrJ
> Reporter: David Smiley
> Priority: Blocker
> Labels: newdev
> Fix For: main (9.0)
>
>
> Solr has had an HTTP/2 based SolrClient since 8.0. Maintaining both HTTP/1
> and HTTP/2 clients is a pain for maintenance of the project as it sometimes
> means duplicative (or partially implemented) work, especially for
> authentication but also sometimes metrics or tracing. Both adds extra
> dependencies for SolrJ and thus our users. It's difficult to grok a codebase
> using two different HTTP client frameworks.
> In this issue, mark HttpSolrClient (and related ones) as deprecated; point to
> HTTP/2 equivalents. Furthermore, mark the Apache "httpcomponents" libs as
> "optional" in the produced Maven pom.xml so that users have to explicitly
> opt-in to use it. Announce this in the Solr users list as well.
> Out of scope to this issue is completely cutting over within Solr itself.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
