I’ve run into this. If my memory serves, I believe group.sort must be explicitly given.
From: Nate R <[email protected]> Date: Monday, October 11, 2021 at 5:41 PM To: [email protected] <[email protected]> Subject: Solr 8.10.0 group.field and sharded servers I have been trying to shard my solr instance over the years to gain performance. Before we weren't able to because of using ngroups in our top queries. I coded away from using ngroups so I was hoping that I would be able to shard my instance and use group.field. Now when I use this particular param. I get 'org.apache.solr.client.solrj.SolrServerException: No live SolrServers available to handle this request'. I have tried using the field as a TEXT, String, and a long. Am I misunderstanding the caveats to grouping and distributing searches? I also tried to use collapsing with "{!collapse field=myField_string}" but of course I got duplicates x the number of shards I have. I have also tore down and completely reinstated my solr instance. Following will give me the error. Commenting out the group.field will make the error go away but of course it does not group. "group": true, "group.field": "myField_string" Is there any way to get unique grouped results while having a distributed index? Thanks, Nate
