[
https://issues.apache.org/jira/browse/SOLR-8078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14902643#comment-14902643
]
Varun Thacker commented on SOLR-8078:
-------------------------------------
bq. But pragmatically, I think switching to _text_ for data driven spell
checking is a reasonable fix to allow data driven to work out of the box with
spell checking.
Would this work or were you hinting at something else?
{code}
curl http://localhost:8983/solr/gettingstarted/config -H
'Content-type:application/json' -d '
{
"add-searchcomponent": {
"name": "myspellcheck",
"class": "solr.SpellCheckComponent",
"queryAnalyzerFieldType": "text_general",
"spellchecker": {
"name": "default",
"field": "_text_",
"classname": "solr.DirectSolrSpellChecker"
}
}
}'
{code}
> Data driven solrconfig spellchecker refers to a non-existent field
> ------------------------------------------------------------------
>
> Key: SOLR-8078
> URL: https://issues.apache.org/jira/browse/SOLR-8078
> Project: Solr
> Issue Type: Bug
> Reporter: Varun Thacker
>
> In the data driven solrconfig.xml file, the "default" spellchecker refers to
> a field called "text" which doesn't exist in the schema.
> Even the "wordbreak" spellchecker refers to a field called "name" which does
> not exist.
> So when you run this query
> {{http://localhost:8983/solr/gettingstarted/spell?q=*}} Solr will throw an
> error.
> I guess the field name should be {{\_text\_}} ?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
