You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2026/06/08 17:53:00 UTC
[jira] [Updated] (SOLR-18243) Refactor: solrj-streaming shouldn't call SolrClientCache.getHttpSolrClient
[ https://issues.apache.org/jira/browse/SOLR-18243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated SOLR-18243:
----------------------------------
Labels: newdev pull-request-available (was: newdev)
> Refactor: solrj-streaming shouldn't call SolrClientCache.getHttpSolrClient
> --------------------------------------------------------------------------
>
> Key: SOLR-18243
> URL: https://issues.apache.org/jira/browse/SOLR-18243
> Project: Solr
> Issue Type: Task
> Components: streaming expressions
> Reporter: David Smiley
> Priority: Major
> Labels: newdev, pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> solrj-streaming calls SolrClientCache.getHttpSolrClient in a number of places, and I believe in each of those cases, the URL comes from a ClusterState that came from a CloudSolrClient. Nowadays, {{org.apache.solr.client.solrj.impl.CloudHttp2SolrClient#getHttpClient}} can be called and then {{requestWithBaseUrl}} on that. If that is too awkward, we can create a temporary HttpSolrClient with a builder that uses the same httpClient from the CloudSolrClient, if coding that is easier (shrug).
--
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