You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/01/05 17:02:00 UTC
[jira] [Commented] (SOLR-15048) collapse + query elevation behaves
inconsistenty w/ 'null group' docs depending on group head selector
[ https://issues.apache.org/jira/browse/SOLR-15048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17259052#comment-17259052 ]
ASF subversion and git services commented on SOLR-15048:
--------------------------------------------------------
Commit a48e937f599bc1487df3321c490589b0d8820616 in lucene-solr's branch refs/heads/master from Chris M. Hostetter
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=a48e937 ]
SOLR-15048: Fixed collapse parser behavior when dealing with docs boosted by QueryElevationComponent that are in the null group to treat them consistently regardless of collapse field type or group head selector
> collapse + query elevation behaves inconsistenty w/ 'null group' docs depending on group head selector
> ------------------------------------------------------------------------------------------------------
>
> Key: SOLR-15048
> URL: https://issues.apache.org/jira/browse/SOLR-15048
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Chris M. Hostetter
> Assignee: Chris M. Hostetter
> Priority: Major
> Attachments: SOLR-15048.patch, SOLR-15048.patch, SOLR-15048.patch, SOLR-15048.patch
>
>
> while working on SOLR-15047, I realized I wasn't really clear on what the _expected_ semantics of were suppose to be when "boosting"
> docs that had null values in the collapse field.
> I expanded on my test from that jira, to demonstrate the logic i (thought) i understood from the Ord based collector - but then discovered that depending on the group head selector used (ie: OrdScoreCollector vs OrdFieldValueCollector+OrdIntStrategy vs OrdFieldValueCollector+OrdValueSourceStrategy , etc...) you get different behavior - not just in what group head is selected, but even when the behavior should be functionally equivilent, you can get different sets of groups. (even for simple string field collapsing, independent of the bugs in numeric field collapsing).
>
> I have not dug into WTF is happening here, but I'll attach my WIP test
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org