[
https://issues.apache.org/jira/browse/SOLR-10263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar Singh updated SOLR-10263:
----------------------------------------
Description:
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) .
*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.
For example:-
*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`.
So related changes have been done at Latest PR. :
https://github.com/apache/lucene-solr/pull/218.
was:
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) .
*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.
For example:-
*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`.
> 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) .
> *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.
> For example:-
> *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`.
> So related changes have been done at Latest PR. :
> https://github.com/apache/lucene-solr/pull/218.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
