You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Alexandre Rafalovitch (JIRA)" <ji...@apache.org> on 2016/10/02 02:21:20 UTC
[jira] [Closed] (SOLR-1917) Possible Null Pointer Exception in
highlight or debug component
[ https://issues.apache.org/jira/browse/SOLR-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexandre Rafalovitch closed SOLR-1917.
---------------------------------------
Resolution: Cannot Reproduce
Ancient bug that may or may not have been triggered by some other ancient code. No longer relevant. If still happens, a new issue can be opened.
> Possible Null Pointer Exception in highlight or debug component
> ---------------------------------------------------------------
>
> Key: SOLR-1917
> URL: https://issues.apache.org/jira/browse/SOLR-1917
> Project: Solr
> Issue Type: Bug
> Components: highlighter
> Affects Versions: 1.4
> Reporter: David Bowen
> Attachments: SOLR-1917.patch
>
>
> This bug may only show up if you have the patch for SOLR-1143 installed, but it should be fixed in any case since the existing logic is wrong. It is explicitly looking for the nulls that can cause the exception, but only after the exception would have already happened.
> What happens is that there is an array of Map.Entry objects which is converted into a SimpleOrderedMap, and then there is a method that iterates over the SimpleOrderedMap looking for null names. That's wrong because it is the array elements themselves which can be null, so constructing the SimpleOrderedMap throws an NPE.
> I will attach a patch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org