Here's my +1 (binding). I ran the smoketester, as well as loading up Solr 10 into the operator and doing a few backups/restores through there.
Best, Jason On Tue, Jan 27, 2026 at 2:17 PM David Smiley <[email protected]> wrote: > > +1 > SUCCESS! [0:59:12.632486] > > I kicked the tires a bit. > I did the docker build and ran it. > > Filed a JIRA issue for an innocuous logged warning: > https://issues.apache.org/jira/browse/SOLR-18089 "embeddedZkServer warning > RE maxCnxns is not configured" > > I went into the admin UI and immediately clicked the link for the new admin > UI. It didn't connect immediately... it has a screen about connecting to a > cluster first. Inconvenient but flexible I guess. So it's default host > value is "http://127.0.0.1:8983/"; but this didn't work for me. Only when I > replaced that IP with "localhost", did it work. I didn't file an issue > yet. Maybe this has something to do with docker/container but I'm > surprised this problem happened at all. The new UI looks nice yet is > extremely incomplete, with major parts grayed out. Well it's > experimental.... > > I consumed the SolrJ artifacts in an app at work to start seeing what the > impact is. More or less expected transition matters, as I was the > instigator of various things like moving some classes around. I wish > CloudSolrClient.Builder had easy methods to customize timeouts, as the > "Legacy" one once did. It's possilbe to do this but it's pretty awkward. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
