[ https://issues.apache.org/jira/browse/SOLR-8078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14902351#comment-14902351 ]
Varun Thacker commented on SOLR-8078: ------------------------------------- Thinking aloud can merge the techproducts and data driven config sets? - To use the {{techproducts}} example , the startup script can post the necessary fields using the schema APIs . So the example config has ManagedSchemaFactory - To use the {{schemaless}} example, the startup script can make sure that the {{add-unknown-fields-to-the-schema}} update chain is used. - We don't need a minimal config set , since all the extra fields in tech products is been added by the startup script and is not present otherwise. [~steve_rowe] what do you think? > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org