[
https://issues.apache.org/jira/browse/LUCENE-9068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17016056#comment-17016056
]
ASF subversion and git services commented on LUCENE-9068:
---------------------------------------------------------
Commit 9d72bfc1afe6d1dc1071d1c24e82a7866767d693 in lucene-solr's branch
refs/heads/master from Alan Woodward
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=9d72bfc ]
LUCENE-9068: Build FuzzyQuery automata up-front (#1042)
FuzzyTermsEnum can now either take an array of compiled automata, and
an AttributeSource, to be used across multiple segments (eg during
FuzzyQuery rewrite); or it can take a term, edit distance, prefix and transition
boolean and build the automata itself if only being used once (eg for fuzzy
nearest neighbour calculations).
Rather than interact via attribute sources and specialized attributes, users of
FuzzyTermsEnum can get the boost and set minimum competitive boosts
directly on the enum.
> Build FuzzyQuery automata up-front
> ----------------------------------
>
> Key: LUCENE-9068
> URL: https://issues.apache.org/jira/browse/LUCENE-9068
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Alan Woodward
> Assignee: Alan Woodward
> Priority: Major
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> FuzzyQuery builds a set of levenshtein automata (one for each possible edit
> distance) at rewrite time, and passes them between different TermsEnum
> invocations using an attribute source. This seems a bit needlessly
> complicated, and also means that things like visiting a query end up building
> the automata again. We should instead build the automata at query
> construction time, which is how AutomatonQuery does it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
