[
https://issues.apache.org/jira/browse/SOLR-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13903495#comment-13903495
]
Shawn Heisey commented on SOLR-5604:
------------------------------------
bq. Let me venture a guess that most (likely all) those configuration
parameters can be chaged at the context or request level without changing
HttpClient itself.
Thank you for the attention and advice!
Here's where I show my ignorance of the inner workings of HttpClient, and tell
you that I have no idea. I see the following HttpSolrServer setters that
modify HttpClient or one of its components. Can all of these be handled with
lower levels that you can change? If they can, then migrating might be easier
than I thought, and we can expose additional knobs without a lot of work.
* setConnectionTimeout
* setSoTimeout
* setAllowCompression
* setFollowRedirects
* setDefaultMaxConnections
* setMaxTotalConnections
HttpClientUtil has all of the options mentioned above, plus these:
* setBasicAuth
* setUseRetry
> Remove deprecations caused by httpclient 4.3.x upgrade
> ------------------------------------------------------
>
> Key: SOLR-5604
> URL: https://issues.apache.org/jira/browse/SOLR-5604
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 4.7
> Reporter: Shawn Heisey
> Fix For: 4.7, 5.0
>
> Attachments: SOLR-5604-4x-just-lucene.patch
>
>
> SOLR-5590 upgraded httpclient in Solr and Lucene to version 4.3.x. This
> version deprecates a LOT of classes and methods, recommending that they all
> be replaced with various methods from the HttpClientBuilder class.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
