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

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

Commit c3dfa68ff9189acd753430a1c61843cbd34a187c in lucene-solr's branch 
refs/heads/branch_8x from Chris M. Hostetter
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=c3dfa68 ]

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-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org

Reply via email to