[
https://issues.apache.org/jira/browse/LUCENE-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-2123:
----------------------------------
Attachment: LUCENE-2123.patch
LUCENE-2123-flex.patch
So the last patch for today.
I optimized the PQ to reuse the ScoreTerm instance when the PQ is full. I think
for current FuzzyQuery the rewrite modes are now as best as possible. The tests
pass that already test the overflow of the PQ by setting BQ.maxClauseCount to
a very low value.
> Move FuzzyQuery rewrite as separate RewriteMode into MTQ, was: Highlighter
> fails to highlight FuzzyQuery
> --------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-2123
> URL: https://issues.apache.org/jira/browse/LUCENE-2123
> Project: Lucene - Java
> Issue Type: Bug
> Components: contrib/highlighter
> Affects Versions: Flex Branch
> Reporter: Uwe Schindler
> Assignee: Uwe Schindler
> Fix For: Flex Branch
>
> Attachments: LUCENE-2123-flex.patch, LUCENE-2123-flex.patch,
> LUCENE-2123-flex.patch, LUCENE-2123-flex.patch, LUCENE-2123-flex.patch,
> LUCENE-2123-flex.patch, LUCENE-2123.patch, LUCENE-2123.patch,
> LUCENE-2123.patch
>
>
> As FuzzyQuery does not allow to change the rewrite mode, highlighter fails
> with UOE in flex since LUCENE-2110, because it changes the rewrite mode to
> Boolean query. The fix is: Allow MTQ to change rewrite method and make
> FUZZY_REWRITE public for that.
> The rewrite mode will live in MTQ as TOP_TERMS_SCORING_BOOLEAN_REWRITE. Also
> the code will be refactored to make heavy reuse of term enumeration code and
> only plug in the PQ for filtering the top terms.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
