[ https://issues.apache.org/jira/browse/SOLR-10846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16104337#comment-16104337 ]
ASF subversion and git services commented on SOLR-10846: -------------------------------------------------------- Commit 1ed8c029670d210a639671f30a1ecd76d71dc784 in lucene-solr's branch refs/heads/branch_7x from [~steve_rowe] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=1ed8c02 ] SOLR-10846: ExternalFileField/FloatFieldSource should throw a clear exception on initialization with a Points-based keyField, which is not supported > 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 > > 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org