[
https://issues.apache.org/jira/browse/LUCENE-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833181#action_12833181
]
Uwe Schindler commented on LUCENE-2261:
---------------------------------------
Hi Robert, patch looks good, all tests pass, nothing to complain from the MTQ
police :-)
There is only one thing unrelated to that issue: It makes no sense to declare
IllegalArgExceptions as they are unchecked. I would remove them, else the
compiler does.
> 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
> Assignee: Robert Muir
> Priority: Minor
> Fix For: Flex Branch, 3.1
>
> Attachments: LUCENE-2261.patch, LUCENE-2261.patch, LUCENE-2261.patch,
> 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: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
