false for the transpositions parameter. At most, this query will match terms up to {@value org.apache.lucene.util.automaton.LevenshteinAutomata#MAXIMUM_SUPPORTED_DISTANCE}edits. Higher distances are not supported. Note that the fuzzy distance is measured in "byte space" on the bytes returned by the {@link org.apache.lucene.analysis.TokenStream}'s {@link org.apache.lucene.analysis.tokenattributes.TermToBytesRefAttribute}, usually UTF8. By default the analyzed bytes must be at least 3 {@link #DEFAULT_MIN_FUZZY_LENGTH} bytes before any edits areconsidered. Furthermore, the first 1 {@link #DEFAULT_NON_FUZZY_PREFIX} byte is not allowed to beedited. We allow up to 1 (@link #DEFAULT_MAX_EDITS} edit. If {@link #unicodeAware} parameter in the constructor is set to true, maxEdits,minFuzzyLength, transpositions and nonFuzzyPrefix are measured in Unicode code points (actual letters) instead of bytes.
NOTE: This suggester does not boost suggestions that required no edits over suggestions that did require edits. This is a known limitation.
Note: complex query analyzers can have a significant impact on the lookup performance. It's recommended to not use analyzers that drop or inject terms like synonyms to keep the complexity of the prefix intersection low for good lookup performance. At index time, complex analyzers can safely be used.
@lucene.experimental | |