[jira] [Resolved] (SOLR-10846) ExternalFileField/FileFloatSource throws NPE if keyField is Points based

["Steve Rowe (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SOLR-10846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Rowe resolved SOLR-10846.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 7.1
                   master (8.0)

I created a follow-on issue to make ExternalFileField support Points-based keyField-s: SOLR-10846.

> ExternalFileField/FileFloatSource throws NPE if keyField is Points based
> ------------------------------------------------------------------------
>
>                 Key: SOLR-10846
>                 URL: https://issues.apache.org/jira/browse/SOLR-10846
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Hoss Man
>            Assignee: Steve Rowe
>            Priority: Blocker
>              Labels: numeric-tries-to-points
>             Fix For: 7.0, master (8.0), 7.1
>
>         Attachments: SOLR-10846.patch, SOLR-10846.patch
>
>
> FileFloatSource (and by extension ExternalFileField) currently throws an NPE if the {{keyField}} is Points based.
> This seems to be due to hardcoded assumptions about {{MultiFields.getTerms(...)}} returning a non-null value for the keyField (which I suspect could also lead to an NPE in situations where the index is completley empty? ... not sure)
> In general, the error handling in FileFloatSource should be improved. 
>  
> If there is no straight forward way to make FileFloatSource work with Point fields, then ExternalFileField should throw a clear error on init if the {{true==keyFieldType.isPointField()}}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org