That makes sense.
It might be interesting at our next community meet up to bring up some of these
“umbrella” tickets and socialize them around, to activate some folks!
> On Apr 30, 2024, at 9:21 AM, Jan Høydahl wrote:
>
> There is an umbrella issue for major SolrJ changes
> https://issues.ap
There is an umbrella issue for major SolrJ changes
https://issues.apache.org/jira/browse/SOLR-15730. Some of the sub tasks are
10.0 only. Could add a rename jira there?
Jan
> 30. apr. 2024 kl. 15:04 skrev Eric Pugh :
>
> Please! It would be nice if someone laid out the work to be done in som
Please! It would be nice if someone laid out the work to be done in some
tickets so folks could pick it up…. Otherwise it looks a bit daunting!
> On Apr 30, 2024, at 7:38 AM, Jan Høydahl wrote:
>
> In Solr 10, SolrJ will have new maven coordinates and the need to explicitly
> pull in solrj-
In Solr 10, SolrJ will have new maven coordinates and the need to explicitly
pull in solrj-xx dependencies. So we coult also do a few key renames such as
"Http2SolrClient" -> "HttpJettySolrClient", while we're busy breaking things :)
Jan
> 30. apr. 2024 kl. 13:21 skrev Jason Gerlowski :
>
> Th
Thanks for summarizing this all David!
We have HttpSolrClientBase AND BaseHttpSolrClient?!
A bit of the messiness here seems like it will resolve itself
"automatically" if we make good on removing the existing deprecations.
(Though given how "entrenched" the Apache client is, that will require
a
It's too bad HttpSolrServer setup this client philosophy. It's momentum was
directly opposite to what you want: a SolrClient that can optionally stream or
load balance and a SolrCloudClient that wraps it.
[Mark Miller - Chat @
Spike](https://spikenow.com/r/a/?ref=spike-organic-signature&_ts=2ki
