[
https://issues.apache.org/jira/browse/SOLR-7084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14312110#comment-14312110
]
Jan Høydahl commented on SOLR-7084:
-----------------------------------
This may not be as severe as I first thought, as the JSON response is well
formed, containing an {{error}} element and no {{msg}} node explaining why. A
more direct handling of the situation where fst==null with a proper msg code
would be good. Perhaps also {{SERVICE_NOT_AVAILABLE}} is better than the
current 500 server error.
> FreeTextSuggester Nullpointer when building dictionary
> ------------------------------------------------------
>
> Key: SOLR-7084
> URL: https://issues.apache.org/jira/browse/SOLR-7084
> Project: Solr
> Issue Type: Bug
> Components: Suggester
> Affects Versions: 4.10.2
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Fix For: 4.10.4, Trunk, 5.1
>
>
> Using {{FreeTextSuggester}}. When starting Solr or reloading core, all
> suggest requests will fail due to a {{Nullpointer}}. There is a {{HTTP 500}}
> response code with the following body. Note that the error returned does not
> have a {{msg}} section but only a trace:
> {code}
> {
> "error":{
> "trace":"java.lang.NullPointerException\n\tat
> org.apache.lucene.search.suggest.analyzing.FreeTextSuggester.lookup(FreeTextSuggester.java:542)\n\tat
>
> org.apache.lucene.search.suggest.analyzing.FreeTextSuggester.lookup(FreeTextSuggester.java:440)\n\tat
>
> org.apache.lucene.search.suggest.analyzing.FreeTextSuggester.lookup(FreeTextSuggester.java:429)\n\tat
>
> org.apache.solr.spelling.suggest.SolrSuggester.getSuggestions(SolrSuggester.java:199)\n\tat
>
> ...
> {code}
> Offending line:
> {code}
> BytesReader bytesReader = fst.getBytesReader();
> {code}
> The fst is null at this time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
