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/06 17:08:01 UTC
[jira] [Commented] (SOLR-15047) 'collapse' on numeric field treats
all docs with '0' in collapse field as part of the null group
[ https://issues.apache.org/jira/browse/SOLR-15047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17259887#comment-17259887 ]
ASF subversion and git services commented on SOLR-15047:
--------------------------------------------------------
Commit 07071ca8e107d184f9dfc2a2271b5dcaaceda650 in lucene-solr's branch refs/heads/master from Chris M. Hostetter
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=07071ca ]
SOLR-15047: Fix collapse parser behavior when collapsing on numeric fields to differentiate '0' group from null group
> 'collapse' on numeric field treats all docs with '0' in collapse field as part of the null group
> ------------------------------------------------------------------------------------------------
>
> Key: SOLR-15047
> URL: https://issues.apache.org/jira/browse/SOLR-15047
> 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-15047.patch, SOLR-15047.patch, SOLR-15047.patch
>
>
> The CollapseQParser has some very, _very_, old code/semantics in it that date back to when the {{FieldCache}} was incapable of differentiating between a document that contained '0' in the field being un-inverted, and a document that didn't have any value in that field.
> This limitation does not exist in DocValues (nor has it existed for a long time) but as the DocValues API has evolved, and as the collapse code has been updated to take advantage of the newer APIs that make it obvious when a document has no value in a field, the collapse code still explicitly equates "0" in a numeric field with the "null group"
> We can/should fix this bug so that the behavior is sane.
> ----
> Known workaround for this problem: (redundantly) index a "string" version of the field being collapsed on - but this is a poor substitute fro being able to efficiently collapse on numeric fields (which take up less space on disk and in the collapse data structures)
--
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