[
https://issues.apache.org/jira/browse/LUCENE-9068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17105588#comment-17105588
]
ASF subversion and git services commented on LUCENE-9068:
---------------------------------------------------------
Commit 05ba52bd21c780692c367c7ea316192047fec4cb in lucene-solr's branch
refs/heads/branch_8_5 from Alan Woodward
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=05ba52b ]
LUCENE-9350: Don't hold references to large automata on FuzzyQuery (#1467)
LUCENE-9068 moved fuzzy automata construction into FuzzyQuery itself. However,
this has the nasty side-effect of blowing up query caches that expect queries
to be
fairly small. This commit restores the previous behaviour of caching the large
automata
on an AttributeSource shared between segments, while making the construction a
bit clearer by factoring it out into a package-private FuzzyAutomatonBuilder.
> 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
> Fix For: 8.5
>
> 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
