[
https://issues.apache.org/jira/browse/SOLR-15078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris M. Hostetter updated SOLR-15078:
--------------------------------------
Attachment: SOLR-15078.patch
Assignee: Chris M. Hostetter
Status: Open (was: Open)
patch with fix and beefed up test coverage
> ExpandComponent treats all docs with '0' in a numeric collapse field the same
> as if null
> ----------------------------------------------------------------------------------------
>
> Key: SOLR-15078
> URL: https://issues.apache.org/jira/browse/SOLR-15078
> 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-15078.patch
>
>
> ExpandComponent has an equivalent to the collapse qparser bug tracked in
> SOLR-15047...
> {quote}...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 [...] 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 [...] code still explicitly equates "0"
> in a numeric field with the "null group"
> {quote}
>
--
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
