Affects Version/s: None
Fix Version/s: None
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 (for relevance or performance reasons) (SUGGEST_WHEN_NOT_IN_INDEX) .
UPDATE : Recently, we also figured out that, for WordBreakSolrSpellChecker also, both - The WordBreak and WordJoin should also have different suggestModes.
We faced this problem in our case, wherein, Most of the WordJoin cases are those where the words individually are valid tokens, but what the users are looking for is actually a combination (wordjoin) of the two tokens.
gold mine sunglasses : Here, both gold and mine are valid tokens. But the actual product being looked for is goldmine sunglasses , where goldmine is a brand.
In such cases, we should recommend didYouMean:goldmine sunglasses . But this wont be possible because we had set SUGGEST_WHEN_NOT_IN_INDEX for WordBreakSolrSpellChecker (of which, WordJoin is a part) .
For this, we should have separate suggestModes for both `wordJoin` as well as `wordBreak`.
Related changes have been done at Latest PR. : https://github.com/apache/lucene-solr/pull/218.