lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] Updated: (LUCENE-2261) configurable MultiTermQuery TopTermsScoringBooleanRewrite pq size
Date Sat, 13 Feb 2010 17:20:27 GMT


Robert Muir updated LUCENE-2261:

    Attachment: LUCENE-2261.patch

bq. 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.

Agreed, here is a patch with this cleanup, and also removes an unused import from MTQ

> configurable MultiTermQuery TopTermsScoringBooleanRewrite pq size
> -----------------------------------------------------------------
>                 Key: LUCENE-2261
>                 URL:
>             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:
For additional commands, e-mail:

View raw message