That sounds like it definitely warrants a Jira. Whoever worked on that API probably forgot about the multiple names cases. Thanks for figuring this out :)
On Fri, Feb 20, 2026 at 6:53 PM Dmitri Maziuk <[email protected]> wrote: > On 2/19/26 17:54, Gus Heck wrote: > > Ah I see now. Did you try sending multiple facet.field elements in the > > JSON? What error did you get? If it's not accepting the simplest > > interpretation, (multiple facet.field elements) then that definitely > needs > > documentation. If it's not accepting any variation, or loosing all but > the > > last one, that would be a bug. > > OK, so it is worse than that: sending an "update-requesthandler" with > > "defaults" : { > "facet.field" : "subject", > "facet.field" : "country", > ... > } > > returns a 200 but checking the handler in /$corename/config shows only > one "facet.field": the first one. > > Whereas sending them as a list: > > "defaults" : { > "facet.field" : ["subject","country", ...] > ... > } > > also returns a 200 but no "facet.field"s are in the config returned by > /$corename/config > > I.e. it's broken both ways. > > > This is using v1 API. At this point I think I'll stick to uploading > solrconfig.xml and reloading the collection. > > Which brings me to another interesting feature that I'll post in a > separate message. > > cheers, > Dima > > -- http://www.needhamsoftware.com (work) https://a.co/d/b2sZLD9 (my fantasy fiction book)
