[
https://issues.apache.org/jira/browse/SOLR-17968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18041527#comment-18041527
]
David Smiley commented on SOLR-17968:
-------------------------------------
Another purpose of an HttpSolrClient is to hold a Builder that either creates a
Jetty or JDK client depending on classpath availability. Basically exactly
what CloudSolrClient.Builder (formerly located in CloudHttp2SolrClient) does,
as of PR #3901 . We can do this in 10.1; it doesn't disturb anything.
> Add HttpSolrClient as base class
> --------------------------------
>
> Key: SOLR-17968
> URL: https://issues.apache.org/jira/browse/SOLR-17968
> Project: Solr
> Issue Type: Improvement
> Components: SolrJ
> Affects Versions: 10.0
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Blocker
> Labels: pull-request-available
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Add HttpSolrClient base class with {{{}getBaseURL(){}}}. HttpSolrClientBase
> (base of Jetty & JDK clients) shall implement it.
> The "old" HttpSolrClient (the implementation using Apache HttpClient) is
> temporarily in the test framework on death row. This issue would rename that
> to HttpApacheSolrClient, and also make it extend HttpSolrClient. There's a
> bit of builder conversion to do, to make that happen there.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
