Having said that, yeah, I wouldn’t build external dependencies on the v2 apis that I didn’t have the ability to tweak from release of Solr to release of Solr.
And I hope that soon we can start having the conversation of taking some of them and removing the experimental label from them, and start at that point deprecating the corresponding V1 apis. We’ll of course need to have a conversation about that and the timelines for keeping the V1 apis, since some folks may have custom tooling using it. If cutting over to the V2 apis in the Admin tool does raise strong concerns, please do speak up! We could deal with concerns via: 1) Doing additional testing (what would that look like/mean?) 2) Only commit to main branch, and not back port to solr 11. 3) Maybe make the V2 apis an opt in in the Admin UI? (Ugh). 4) Only do v2 in say the CLI or the new Solr UI We do have multiple PR’s in flight to move the CLI to the new strongly type V2 apis as well…. > On Aug 10, 2026, at 12:22 PM, David Smiley <[email protected]> wrote: > > Given the experimental status of our V2 APIs; is this good? Maybe some of > our V2 APIs are more stable than others. > > On Mon, Aug 10, 2026 at 9:48 AM Eric Pugh <[email protected]> > wrote: > > > Hey all, just wanted to make sure folks are aware of > > https://github.com/apache/solr/pull/4659 > > <https://github.com/apache/solr/pull/4659> which starts cutting over the > > Admin UI to our V2 apis. I only picked the “easy” APIs to cut over in > > this first batch, and it was pretty easy to leverage some AI for this > > fairly rote migration. I tried NOT to try and improve the Admin UI beyond > > > > Once this is merged, I’m also going to take a pass through our new Solr UI > > and see if there are some opportunities there to move to the V2 apis as > > well. > > > > ERic > > > > Disclaimer > > > > The information contained in this communication from the sender is > > confidential. It is intended solely for use by the recipient and others > > authorized to receive it. If you are not the recipient, you are hereby > > notified that any disclosure, copying, distribution or taking action in > > relation of the contents of this information is strictly prohibited and may > > be unlawful. > > > > This email has been scanned for viruses and malware, and may have been > > automatically archived by Mimecast, a leader in email security and cyber > > resilience. Mimecast integrates email defenses with brand protection, > > security awareness training, web security, compliance and other essential > > capabilities. Mimecast helps protect large and small organizations from > > malicious activity, human error and technology failure; and to lead the > > movement toward building a more resilient world. To find out more, visit > > our website. > > Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast, a leader in email security and cyber resilience. Mimecast integrates email defenses with brand protection, security awareness training, web security, compliance and other essential capabilities. Mimecast helps protect large and small organizations from malicious activity, human error and technology failure; and to lead the movement toward building a more resilient world. To find out more, visit our website.
