lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Male (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3381) Sandbox remaining contrib queries
Date Thu, 18 Aug 2011 09:15:33 GMT


Chris Male commented on LUCENE-3381:

I have thousands of people using it daily in dozens of different installations so keen to
avoid any significant changes/loss.

I have no intention of removing it but as Robert has pointed out in a couple of issues there
is huge scope for improvement which we cannot ignore.  I'll make sure to document any changes.

- the fact it caches 'rewrittenQuery' in the QUERY itself, this means the Query is keeping
IndexSearcher-dependent state in the Query: this is broken.
- the static similarity, which at the moment must extend TFIDFSimilarity (does not work with
other scoring systems)

Good points.  The cached rewrittenQuery seems like an easy fix (albeit a change that should
be documented).  I see your comments in code about averaging out statistics.  That seems like
a bigger issue.  Moving away from a static similarity seems like its doable at this stage.
 Is the agnostic scoring model support a showstopper?

> Sandbox remaining contrib queries
> ---------------------------------
>                 Key: LUCENE-3381
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Chris Male
>         Attachments: LUCENE-3381.patch
> In LUCENE-3271, I moved the 'good' queries from the queries contrib to new destinations
(primarily the queries module).  The remnants now need to find their home.  As suggested in
LUCENE-3271, these classes are not bad per se, just odd.  So lets create a sandbox contrib
that they and other 'odd' contrib classes can go to.  We can then decide their fate at another

This message is automatically generated by JIRA.
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message