See http://hudson.zones.apache.org/hudson/job/Solr-trunk/358/changes
Deprecate SpellCheckRequestHandler replace with one that does query analysis
and spell checks each token
Key: SOLR-485
URL:
[
https://issues.apache.org/jira/browse/SOLR-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated SOLR-485:
-
Affects Version/s: 1.2
Fix Version/s: 1.3
Assignee: Grant Ingersoll
[
https://issues.apache.org/jira/browse/SOLR-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12571992#action_12571992
]
Yonik Seeley commented on SOLR-303:
---
Patrick, I've reproduced your null pointer exception
: Which leads me to the next question, in the extendedResults, shouldn't it use
: the Query analyzer for the spellcheck field to tokenize the terms instead of
: splitting on the space character?
this question came up a little while back, and i made the same suggestion
... but Mike disagreed.
: If we hook it into the nightly target, then the only thing that needs to be
: done is make sure Hudson captures the reports. The trick in hooking it into
: the nightly is that you want to make sure you clean before doing any other
: packaging to make sure that the instrumented files are not in
