[jira] [Commented] (SOLR-5111) Change SpellCheckComponent default analyzer when queryAnalyzerFieldType is not defined
[ https://issues.apache.org/jira/browse/SOLR-5111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14071905#comment-14071905 ] Varun Thacker commented on SOLR-5111: - [~jdyer] - Any thoughts on this one? Change SpellCheckComponent default analyzer when queryAnalyzerFieldType is not defined -- Key: SOLR-5111 URL: https://issues.apache.org/jira/browse/SOLR-5111 Project: Solr Issue Type: Improvement Reporter: Varun Thacker Priority: Minor Fix For: 4.9, 5.0 Attachments: SOLR-5111.patch In the collection1 example, the SpellCheckComponent uses the query analyzer of text_general FieldType. If queryAnalyzerFieldType is removed from the configuration a WhitespaceAnalyzer is used by default. I suggest we could change the default to SimpleAnalyzer so that foo and Foo gives the same results and log that the analyzer is missing. Also are there more places in solrconfig which have dependencies on schema like this? -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-5111) Change SpellCheckComponent default analyzer when queryAnalyzerFieldType is not defined
[ https://issues.apache.org/jira/browse/SOLR-5111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14072006#comment-14072006 ] James Dyer commented on SOLR-5111: -- It makes sense to me that we should do this. The only caution is you could break someone's config in the case they were depending on WhitespaceAnalyzer. I can't imagine this is what anyone would want, but you can never underestimate Users. Change SpellCheckComponent default analyzer when queryAnalyzerFieldType is not defined -- Key: SOLR-5111 URL: https://issues.apache.org/jira/browse/SOLR-5111 Project: Solr Issue Type: Improvement Reporter: Varun Thacker Priority: Minor Fix For: 4.9, 5.0 Attachments: SOLR-5111.patch In the collection1 example, the SpellCheckComponent uses the query analyzer of text_general FieldType. If queryAnalyzerFieldType is removed from the configuration a WhitespaceAnalyzer is used by default. I suggest we could change the default to SimpleAnalyzer so that foo and Foo gives the same results and log that the analyzer is missing. Also are there more places in solrconfig which have dependencies on schema like this? -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-5111) Change SpellCheckComponent default analyzer when queryAnalyzerFieldType is not defined
[ https://issues.apache.org/jira/browse/SOLR-5111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13727472#comment-13727472 ] Varun Thacker commented on SOLR-5111: - Simple patch. Change SpellCheckComponent default analyzer when queryAnalyzerFieldType is not defined -- Key: SOLR-5111 URL: https://issues.apache.org/jira/browse/SOLR-5111 Project: Solr Issue Type: Improvement Reporter: Varun Thacker Priority: Minor Fix For: 4.5, 5.0 Attachments: SOLR-5111.patch In the collection1 example, the SpellCheckComponent uses the query analyzer of text_general FieldType. If queryAnalyzerFieldType is removed from the configuration a WhitespaceAnalyzer is used by default. I suggest we could change the default to SimpleAnalyzer so that foo and Foo gives the same results and log that the analyzer is missing. Also are there more places in solrconfig which have dependencies on schema like this? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
