Dear Wiki user, You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.
The "SpellCheckComponent" page has been changed by YonikSeeley. The comment on this change is: move build on commit, etc, to configuration.. http://wiki.apache.org/solr/SpellCheckComponent?action=diff&rev1=38&rev2=39 -------------------------------------------------- The SpellCheckComponent is designed to provide inline spell checking of queries without having to issue separate requests. Another and possibly clearer way of stating this is that it makes query suggestions (as do well-known web search engines), for example if it thinks the input query might have been misspelled. (Some people tend to think that "spellchecker" is actually a misnomer, and something along the lines of "query suggest" would have been more appropriate.) - The SpellCheckComponent can use the [[http://wiki.apache.org/jakarta-lucene/SpellChecker|Lucene SpellChecker]] to give suggestion for given words, or one can implement their own spell checker using the SolrSpellChecker abstract base class. + The SpellCheckComponent can use the [[http://wiki.apache.org/jakarta-lucene/SpellChecker|Lucene SpellChecker]] to give suggestion for given words, or one can implement their own spell checker in Java using the !SolrSpellChecker abstract base class. = Quick Start = The example server is configured with a request handler that uses the SpellCheckComponent. @@ -129, +129 @@ * org.apache.solr.spelling.IndexBasedSpellChecker -- Create and use a spelling dictionary that is based on the Solr index or an existing Lucene index * org.apache.solr.spelling.FileBasedSpellChecker -- Create and use a spelling dictionary based off a flat file. This can be useful for using Solr as a spelling server or in other instances when spelling suggestions do not need to be based on the content of an actual index. + <<Anchor(onCommit)>> + == Building on Commits == + SpellCheckComponent can be configured to automatically (re)build indices based on fields in Solr index when a commit is done. In order to do so you must enable this feature by adding the following line in your SpellCheckComponent configuration for each spellchecker where you wish it to apply: + {{{ + <str name="buildOnCommit">true</str> + }}} + + For example: + {{{ + <lst name="spellchecker"> + <str name="name">default</str> + <str name="field">spell</str> + <str name="spellcheckIndexDir">./spellchecker1</str> + <str name="buildOnCommit">true</str> + </lst> + }}} + + <<Anchor(onOptimize)>> + == Building on Optimize == + + <!> [[Solr1.4]] + + SpellCheckComponent can be configured to automatically (re)build indices based on fields in Solr index when an optimize command is done. In order to do so you must enable this feature by adding the following line in your SpellCheckComponent configuration + {{{ + <str name="buildOnOptimize">true</str> + }}} + = Spell Checking Analysis = SpellCheckingAnalysis - Provides details on how Analysis and Spell Checking work together @@ -322, +349 @@ The existing converter uses a relatively simple Regex to extract out the basic query terms from a query and create tokens from them. - <<Anchor(onCommit)>> - = Building on Commits = - SpellCheckComponent can be configured to automatically (re)build indices based on fields in Solr index when a commit is done. In order to do so you must enable this feature by adding the following line in your SpellCheckComponent configuration for each spellchecker where you wish it to apply - {{{ - <str name="buildOnCommit">true</str> - }}} - - For example: - {{{ - <lst name="spellchecker"> - <str name="name">default</str> - <str name="field">spell</str> - <str name="spellcheckIndexDir">./spellchecker1</str> - <str name="buildOnCommit">true</str> - </lst> - }}} - - <<Anchor(onOptimize)>> - = Building on Optimize = - - <!> [[Solr1.4]] - - SpellCheckComponent can be configured to automatically (re)build indices based on fields in Solr index when an optimize command is done. In order to do so you must enable this feature by adding the following line in your SpellCheckComponent configuration - {{{ - <str name="buildOnOptimize">true</str> - }}} = History = For discussion of the development of this feature, see [[https://issues.apache.org/jira/browse/SOLR-572|SOLR-572]].
