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

Shalin Shekhar Mangar updated SOLR-648:
---------------------------------------

    Attachment: SOLR-648.patch

Added testcase as SpellCheckComponentTest#testReloadOnStart which reproduces 
the bug reported in this issue.

Grant, would you like to review this patch? It contains minor API change so 
you'll need to revisit the custom SolrSpellChecker implementation you had. I'd 
like to commit this asap so that I can continue with SOLR-622.

An alternate way would have been to change the signature of the 
SolrSpellChecker.reload method to take in atleast the SolrCore or the same 
params as the build method.

> SpellcheckComponent throws NullPointerException on restart without build
> ------------------------------------------------------------------------
>
>                 Key: SOLR-648
>                 URL: https://issues.apache.org/jira/browse/SOLR-648
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 1.3
>            Reporter: Geoffrey Young
>            Assignee: Shalin Shekhar Mangar
>             Fix For: 1.3
>
>         Attachments: SOLR-648.patch, SOLR-648.patch, SOLR-648.patch
>
>
> from 
> http://mail-archives.apache.org/mod_mbox/lucene-solr-user/200807.mbox/[EMAIL 
> PROTECTED]
> "I believe there is a bug in IndexBased- and FileBasedSpellChecker.java
> where the analyzer variable is only set on the build command. Therefore,
> when the index is reloaded, but not built after starting solr, issuing a
> query with the spellcheck.q parameter will cause a NullPointerException to
> be thrown (SpellCheckComponent.java:158). Moving the analyzer logic to the
> constructor seems to fix the problem."

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to