Issue with expand feature in collapse/expand result set workflow

Hi, I am using Solr 8.5.2 (non-SolrCloud) mode. It is a non-sharded scenario. I am trying to collapse the resultset based on one of the string fields (say X). Collapse query works as expected. It collapses the result set by excluding the documents that have the same field X and retains only the to

Re: Issue with expand feature in collapse/expand result set workflow

Did you try expand.rows parameter for how many items to include in each group? https://solr.apache.org/guide/8_7/collapse-and-expand-results.html Regards, Alex. On Thu, 20 May 2021 at 13:02, gnandre wrote: > > Hi, > > I am using Solr 8.5.2 (non-SolrCloud) mode. It is a non-sharded scenario. I

Re: Issue with expand feature in collapse/expand result set workflow

Depending on what your goals/expectations are, it could also be worth noting the `expand.q` and `expand.fq` params, which are applied when fetching "expanded docs" (intersecting with the union of `expand.field` result values). In cases where you want to "pivot" to an unrestricted set of related clu

geodist sort not working - release 8.8.2

Hi , *Solr release 8.8.2, Ubuntu. I am trying to run a query and getting rows sorted by geodist and got the following error: sort param could not be parsed as a query, and is not a field that exists in the index: geodist() Quick example: &q=*:* &sfield=location &pt=42.352455,-71.048069 &sort

Re: Issue with expand feature in collapse/expand result set workflow

Alexandre, I did not because the default value of 5 was sufficient for the number of results I am getting back. It is a result set of 7 documents total and each group should have at max 2 documents in my case. Groping feature (as opposed to collapse-expand feature) is working as expected. I am not

SOLR Cel throws an error when parsing Images

Hi, I'm using ExtractingRequestHandler and Solr CEL to extract data from files. And I'm getting an error when uploading images (jpeg, tiff, png), but otherwise PDF, docs, xlsx etc have no problems. So what's happening is the server thinks the date (probably the archive_dt field because that fiel

TimeSeries Data

Hi, We are using Routed Alias . We had an incident where there was a node in the cluster and we had to replace it. After replacing the node we created the collections on the new node as replicas. System is back operational but we are seei