Non security breaking change would now be for 11.x Also, at some point we should update all the "repeated key" use cases, which while legal JSON are super annoying to deal with because many json parsers are built to convert JSON to map structures by default.
As for requiring legal JSON: +1 On Mon, Apr 27, 2026 at 1:18 PM Christos Malliaridis < [email protected]> wrote: > Hello everyone, > > During the development of the new UI I noticed that the JSON parsing in our > API is configured to be lenient. This means that it allows for example > numbers being provided for fields that are normally strings. > > During some tests I found out that this behavior throws errors for some > specific cases. I have documented those in SOLR-18191 [1]. > > I would like to change the request parsing for JSON input to be strict and > not lenient. Renato Haebrli has already created a draft PR [2] where this > is being addressed. > > Since this may be considered a breaking change, I would like to gather more > opinions and consensus before changing the behavior in 10.x. If it is > considered a problematic change, we could work out a migration plan. > > What do you think about the proposed change? And do you think consumers > actually are affected by this? > > Best, > Christos > > [1] SOLR-18191 https://issues.apache.org/jira/browse/SOLR-18191 > [2] https://github.com/apache/solr/pull/4329 > -- http://www.needhamsoftware.com (work) https://a.co/d/b2sZLD9 (my fantasy fiction book)
