[
https://issues.apache.org/jira/browse/LUCENE-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832607#action_12832607
]
Uwe Schindler commented on LUCENE-2261:
---------------------------------------
Patch looks good, some things because of serializable:
- The readResove method must go to the singleton constant, which should also
throw UOE when modified
- euquals / hashcode is neaded for the rewritemode, else FuzzyQuery & Co would
no longer compare
It could be solved by doing like for AutoRewrite and its unmodifiable constant.
I know: Queries are a pain because of Serializable.
+1 on adding a param to FuzzyQuery ctor
> configurable MultiTermQuery TopTermsScoringBooleanRewrite pq size
> -----------------------------------------------------------------
>
> Key: LUCENE-2261
> URL: https://issues.apache.org/jira/browse/LUCENE-2261
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Search
> Reporter: Robert Muir
> Priority: Minor
> Fix For: Flex Branch, 3.1
>
> Attachments: LUCENE-2261.patch
>
>
> MultiTermQuery has a TopTermsScoringBooleanRewrite, that uses a priority
> queue to expand the query to the top-N terms.
> currently N is hardcoded at BooleanQuery.getMaxClauseCount(), but it would be
> nice to be able to set this for top-N MultiTermQueries: e.g. expand a fuzzy
> query to at most only the 50 closest terms.
> at a glance it seems one way would be to expose TopTermsScoringBooleanRewrite
> (it is private right now) and add a ctor to it, so a MultiTermQuery can
> instantiate one with its own limit.
--
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: [email protected]
For additional commands, e-mail: [email protected]
