Thank you, Shawn. I'm now using a custom HttpClient that I create in a
similar manner as SolrJ, and it works quite well.
Of course, a fix in a future release would be great, so that we can
remove the workaround eventually.
Thanks,
Andreas
Shawn Heisey schrieb am 10.10.2018 um 16:31:
On 10/1/2018 6:54 AM, Andreas Hubold wrote:
Is there some other way to configure an HTTP proxy, e.g. with
HttpSolrClient.Builder? I don't want to create an Apache HttpClient
instance myself but the builder from Solrj (HttpSolrClient.Builder).
Unless you want to wait for a fix for SOLR-12848, you have two options:
1) Use a SolrJ client from 6.6.x, before the fix for SOLR-4509. If
you're using HttpSolrClient rather than CloudSolrClient, a SolrJ major
version that's different than your Solr major version won't be a big
problem. Large version discrepancies can be very problematic with the
Cloud client.
2) Create a custom HttpClient instance with the configuration you want
and use that to build your SolrClient instances. If you're using the
Solr client in a multi-threaded manner, you'll want to be sure that
the HttpClient is defined to allow enough threads -- it defaults to two.
I do think this particular problem is something we should fix. But
that doesn't help you in the short term. It could take several weeks
(or maybe longer) for a fix from us to arrive in your hands, unless
you're willing to compile from source.
Thanks,
Shawn
