基于SOLR-Spellchecker实现多字符补全的配置优化问询

需求描述 #

希望通过Solr实现类似谷歌的自动补全功能：输入部分字符（如“chocol”）时，返回补充多个字符的候选词，例如“chocolate”“chocolissimo”“chocolate cake”等。

当前配置 #

{
  "searchComponent":{
    "name": "spellcheckXXX",
    "class": "solr.SpellCheckComponent",
    "queryAnalyzerFieldType": "text_general",
    "spellchecker": {
        "name": "default",
        "field": "multi_term_lowercase_suggestion",
        "classname": "solr.DirectSolrSpellChecker",
        "distanceMeasure": "internal",
        "maxEdits":1,
        "minPrefix":1,
        "minQueryLength":3,
        "combineWords": "true",
        "comparatorClass": "freq"
    }
}

{
  "requestHandler":{
    "name":"/spellcheckXXX",
    "class":"solr.SearchHandler",
    "startup":"lazy",
    "defaults":{ 
        "spellcheck":"true",
        "spellcheck.dictionary":"default",
        "spellcheck.extendedResults":"true",
        "spellcheck.count":"50",
        "spellcheck.alternativeTermCount":"2",
        "spellcheck.maxResultsForSuggest":"50",
        "spellcheck.collate":"true",
        "spellcheck.collateExtendedResults":"true",
        "spellcheck.maxCollationTries":"100",
        "spellcheck.maxCollations":"50",
        "spellcheck.onlyMorePopular":"true",
        "rows": 0,
        "df": "multi_term_lowercase_suggestion"
    },
    "last-components":["spellcheckXXX"]
}

<field name="multi_term_lowercase_suggestion" type="multi_term_lowercase_suggestion_text" indexed="true" stored="true"/>

<fieldType name="multi_term_lowercase_suggestion_text" class="solr.TextField" positionIncrementGap="100">
    <analyzer>
      <tokenizer class="solr.StandardTokenizerFactory"/>
      <filter class="solr.LowerCaseFilterFactory"/>
    </analyzer>
</fieldType>

当前问题 #

现有配置偏向拼写纠错，仅能补充单个字符或替换字符：输入德语词“Schokol”（完整词为Schokolade）时，返回“school”和“schoko”，而非“schokolade”；只有输入“Schokolad”时，才会得到“schokolade”的建议。

解决方案 #

方案一：改用SuggestComponent（推荐） #

SpellCheckComponent核心是拼写纠错，自动补全更适合用SuggestComponent，它专门针对前缀匹配、预测补全场景优化。

1. 替换SearchComponent配置

{
  "searchComponent": {
    "name": "suggest",
    "class": "solr.SuggestComponent",
    "suggester": {
      "name": "default",
      "class": "solr.FuzzySuggester",
      "lookupImpl": "org.apache.solr.spelling.suggest.fst.WFSTLookupFactory",
      "field": "multi_term_lowercase_suggestion",
      "buildOnCommit": true,
      "minPrefix": 3,
      "maxEdits": 2,
      "suggestAnalyzerFieldType": "multi_term_lowercase_suggestion_text"
    }
  }
}

2. 替换RequestHandler配置

{
  "requestHandler": {
    "name": "/suggest",
    "class": "solr.SearchHandler",
    "startup": "lazy",
    "defaults": {
      "suggest": "true",
      "suggest.dictionary": "default",
      "suggest.count": 50,
      "suggest.collate": "false",
      "rows": 0
    },
    "components": ["suggest"]
  }
}

方案二：调整现有SpellCheckComponent参数 #

如果不想更换组件，可修改以下参数实现多字符补全：

1. 修改SearchComponent参数

{
  "searchComponent": {
    "name": "spellcheckXXX",
    "class": "solr.SpellCheckComponent",
    "queryAnalyzerFieldType": "multi_term_lowercase_suggestion_text",
    "spellchecker": {
      "name": "default",
      "field": "multi_term_lowercase_suggestion",
      "classname": "solr.DirectSolrSpellChecker",
      "distanceMeasure": "internal",
      "maxEdits": 3, // 提高允许的编辑距离，支持补充多个字符
      "minPrefix": 3,
      "minQueryLength": 3,
      "combineWords": "true",
      "comparatorClass": "freq",
      "maxInspections": 1000, // 增加候选词检查数量
      "onlyMorePopular": false // 关闭仅返回更流行结果的限制
    }
  }
}

2. 修改RequestHandler参数

在defaults中修改：

"spellcheck.onlyMorePopular": "false"

该参数会过滤掉热度低于查询词的结果，而“schokolade”可能热度不如“schoko”，关闭后可返回完整补全词。

方案三：优化字段类型（支持多词补全） #

若需返回“chocolate cake”这类多词短语补全，需调整字段分析器，将整个短语作为单个词条处理：

<fieldType name="multi_term_lowercase_suggestion_text" class="solr.TextField" positionIncrementGap="100">
    <analyzer type="index">
      <tokenizer class="solr.KeywordTokenizerFactory"/>
      <filter class="solr.LowerCaseFilterFactory"/>
    </analyzer>
    <analyzer type="query">
      <tokenizer class="solr.KeywordTokenizerFactory"/>
      <filter class="solr.LowerCaseFilterFactory"/>
    </analyzer>
</fieldType>

内容的提问来源于stack exchange，提问作者Onyxelfe