Coincidentally, I was just made aware of this ticket that may be of interest here: https://issues.apache.org/jira/browse/SOLR-14687 There is a PR now too: https://github.com/apache/solr/pull/4206
On Thu, Mar 12, 2026 at 1:49 PM Mikhail Khludnev <[email protected]> wrote: > On Thu, Mar 12, 2026 at 6:33 PM Dmitri Maziuk <[email protected]> > wrote: > > > Ah, thank you. It'd be nice if it errored out like many other things do > > now instead of returning all/some documents like they did in v.8. > > > > There's no one-size-fits-all rule to distinguish between right and wrong > filters. As I understand it, the team is moving toward schema and path > fields/filters, but that's where I'm getting lost. > > > > > > As it turns out, the problem I was actually trying to solve was the new > > "overlay" config API thing: our custom handler had a list of default > > `fq`s that got squashed when I tried to update it via the API, and that > > was stuck in the overlay.json. It took a few tries before I realized why > > updates to solrconfig.xml are not taking. But now the `which="*:* ...` > > is in there too. > > > > Anyway, thanks again, > > Dima > > > > > > -- > Sincerely yours > Mikhail Khludnev > -- http://www.needhamsoftware.com (work) https://a.co/d/b2sZLD9 (my fantasy fiction book)
