You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "Tomas Eduardo Fernandez Lobbe (Jira)" <ji...@apache.org> on 2021/04/20 04:19:00 UTC
[jira] [Resolved] (SOLR-15155) Let CloudHttp2SolrClient accept an
external Http2SolrClient Builder
[ https://issues.apache.org/jira/browse/SOLR-15155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomas Eduardo Fernandez Lobbe resolved SOLR-15155.
--------------------------------------------------
Fix Version/s: 8.9
main (9.0)
Resolution: Fixed
> Let CloudHttp2SolrClient accept an external Http2SolrClient Builder
> -------------------------------------------------------------------
>
> Key: SOLR-15155
> URL: https://issues.apache.org/jira/browse/SOLR-15155
> Project: Solr
> Issue Type: Improvement
> Reporter: Tomas Eduardo Fernandez Lobbe
> Assignee: Tomas Eduardo Fernandez Lobbe
> Priority: Minor
> Fix For: main (9.0), 8.9
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> {{CloudHttp2SolrClient}} doesn't provide much of the options that {{Http2SolrClient}} does (timeouts, max connections per hosts, etc). Technically it accepts a fully built {{Http2SolrClient}}, however, in such case the client becomes "external", which means it won't be closed when the CloudClient is closed (one needs to maintain a reference and close explicitly after closing CloudClient).
> {{CloudHttp2SolrClient}} will use an empty/default {{Http2SolrClient.Builder}} to build it's internal client. I propose we allow providing a configured {{Http2SolrClient.Builder}} instead and let the {{CloudHttp2SolrClient}} just build from it. This would be optional of course, and backwards compatible.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org