[
https://issues.apache.org/jira/browse/SOLR-10263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15945380#comment-15945380
]
Amrit Sarkar edited comment on SOLR-10263 at 3/28/17 3:28 PM:
--------------------------------------------------------------
I am not sure whether it is a popular use case or not at this moment, and maybe
changing the current implementation to accommodate this will make things
complicated.
bq. Any suggestions on how you would like to see the configuration in
solrconfig.xml?
I can see the patch now. Overriding parameters makes sense.
was (Author: [email protected]):
I am not sure whether it is a popular use case or not at this moment, and maybe
changing the current implementation to accommodate this will make things
complicated. Any suggestions on how you would like to see the configuration in
solrconfig.xml?
> Different SpellcheckComponents should have their own suggestMode
> ----------------------------------------------------------------
>
> Key: SOLR-10263
> URL: https://issues.apache.org/jira/browse/SOLR-10263
> Project: Solr
> Issue Type: Wish
> Security Level: Public(Default Security Level. Issues are Public)
> Components: spellchecker
> Reporter: Abhishek Kumar Singh
> Priority: Minor
>
> As of now, common spellcheck options are applied to all the
> SpellCheckComponents.
> This can create problem in the following case:-
> It may be the case that we want *DirectSolrSpellChecker* to ALWAYS_SUGGEST
> spellcheck suggestions.
> But we may want *WordBreakSpellChecker* to suggest only if the token is not
> in the index (SUGGEST_WHEN_NOT_IN_INDEX) .
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
