[ 
https://issues.apache.org/jira/browse/SOLR-18195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18074476#comment-18074476
 ] 

ASF subversion and git services commented on SOLR-18195:
--------------------------------------------------------

Commit ef75ab82a5a8ee56a64e2bc70302904fcf86c8dd in solr's branch 
refs/heads/main from Sonu Sharma
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=ef75ab82a5a ]

SOLR-18195: CombinedQueryComponent supports Collapse now (#4277)

Support for using {!collapse} with CombinedQueryComponent (RRF)

> Support for Collapse Results in Combined Query Component
> --------------------------------------------------------
>
>                 Key: SOLR-18195
>                 URL: https://issues.apache.org/jira/browse/SOLR-18195
>             Project: Solr
>          Issue Type: Improvement
>          Components: vector-search
>            Reporter: Sonu Sharma
>            Priority: Minor
>              Labels: pull-request-available
>          Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> With reference to previous new Query Component Feature:  
> https://issues.apache.org/jira/browse/SOLR-17319
> When using \{!collapse} with CombinedQueryComponent (hybrid search / RRF), 
> duplicate documents appear in the result set for the same collapse field 
> value. Each sub-query independently collapses correctly via 
> CollapsingPostFilter, but simpleCombine() merges results by Lucene doc ID 
> only - it has no awareness of the collapse field. Different sub-queries may 
> select different group heads for the same field value, and both survive the 
> merge.
> However it is well know limitation that :[ "In order to use these features 
> with SolrCloud, the documents must be located on the same 
> shard."|https://solr.apache.org/guide/solr/latest/query-guide/collapse-and-expand-results.html]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to