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

Reply via email to