https://issues.apache.org/jira/browse/SOLR-16723 and MR posted.
Kevin Risden
On Tue, Mar 28, 2023 at 3:34 PM Houston Putman wrote:
> I agree we shouldn't need the apache client when jetty is used. But making
> Apache and Jetty implementations of the APIs is a big ask, and I'm not sure
> it's w
I agree we shouldn't need the apache client when jetty is used. But making
Apache and Jetty implementations of the APIs is a big ask, and I'm not sure
it's worth the maintenance effort.
- Houston
On Tue, Mar 28, 2023 at 3:32 PM Kevin Risden wrote:
> This was introduced here -
>
> https://github
This was introduced here -
https://github.com/apache/solr/commit/8efed0555898f485d435d53a72cb6441507d81e1#diff-db379c74efc9ff28acfd7571b07e16dbcdaa510783f2bee835b4a288927b5b3d
It looks like it inadvertently copied from HttpSolrClient.java and
used ContentType.parse(ct).getMimeType() instead
of Mim
Good find! I’d say create a jira on making solrj client side work with apache
client excluded. Makes sense.
Jan Høydahl
> 28. mar. 2023 kl. 07:04 skrev Shawn Heisey :
>
> I have some simple solrj code pulling in solrj 9.2.0 that creates a client
> (Http2SolrClient) and then uses that to send
