lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erick Erickson (JIRA)" <>
Subject [jira] [Resolved] (LUCENE-1190) a lexicon object for merging spellchecker and synonyms from stemming
Date Sun, 10 Mar 2013 13:29:12 GMT


Erick Erickson resolved LUCENE-1190.

    Resolution: Won't Fix

SPRING_CLEANING_2013 We can reopen if necessary.
> a lexicon object for merging spellchecker and synonyms from stemming
> --------------------------------------------------------------------
>                 Key: LUCENE-1190
>                 URL:
>             Project: Lucene - Core
>          Issue Type: New Feature
>          Components: core/search, modules/other
>    Affects Versions: 2.3
>            Reporter: Mathieu Lecarme
>            Assignee: Otis Gospodnetic
>         Attachments: aphone+lexicon.patch, aphone+lexicon.patch
> Some Lucene features need a list of referring word. Spellchecking is the basic example,
but synonyms is an other use. Other tools can be used smoothlier with a list of words, without
disturbing the main index : stemming and other simplification of word (anagram, phonetic ...).
> For that, I suggest a Lexicon object, wich contains words (Term + frequency), wich can
be built from Lucene Directory, or plain text files.
> Classical TokenFilter can be used with Lexicon (LowerCaseFilter and ISOLatin1AccentFilter
should be the most useful).
> Lexicon uses a Lucene Directory, each Word is a Document, each meta is a Field (word,
ngram, phonetic, fields, anagram, size ...).
> Above a minimum size, number of differents words used in an index can be considered as
stable. So, a standard Lexicon (built from wikipedia by example) can be used.
> A similarTokenFilter is provided.
> A spellchecker will come soon.
> A fuzzySearch implementation, a neutral synonym TokenFilter can be done.
> Unused words can be remove on demand (lazy delete?)
> Any criticism or suggestions?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message