Just to say, I've been writing a smoke test for the v2 APIs when I've had a spare hour, I've done about half of it https://github.com/apache/solr/pull/3023/files <https://github.com/apache/solr/pull/3023/files#diff-549531110b26fa08a870f1853351abad4808116ff4258b5226358d6a5073dadb> I've found three broken endpoints so far; hopefully I'll finish writing the test this weekend and see if there's any more.
>From a consumer POV what I have noticed is that the validation of the requests is slightly brutal, in that invalid input (missing fields, object instead of an array etc) leads to a 500 response rather than a 400. It would be good to distinguish bad request errors from backend errors. A *nice to have*, would be to return the error in the response (e.g. using RFC 7807 / RFC 9457 error responses), so that the client author doesn't have to go to the server log when they get it wrong. On Tue, 11 Feb 2025 at 02:13, David Smiley <dsmiley....@gmail.com> wrote: > (An aside: discussion around a particular endpoint or even category of > endpoints deserves its own thread IMO) > > > On Feb 10, 2025, at 4:40 PM, Christos Malliaridis < > malliari...@apache.org> wrote: > > - If this assumption is correct, can one update the log level of all > nodes with a single request? > > I can say Solr supports this, _at least_ in the V1 API, as I was involved > as a reviewer. > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org > For additional commands, e-mail: dev-h...@solr.apache.org > >
