lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Male (JIRA)" <>
Subject [jira] [Resolved] (LUCENE-3256) Consolidate CustomScoreQuery, ValueSourceQuery and BoostedQuery
Date Thu, 30 Jun 2011 02:33:28 GMT


Chris Male resolved LUCENE-3256.

    Resolution: Fixed
      Assignee: Chris Male

Committed revision 1141366.

> Consolidate CustomScoreQuery, ValueSourceQuery and BoostedQuery 
> ----------------------------------------------------------------
>                 Key: LUCENE-3256
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Sub-task
>          Components: core/search
>            Reporter: Chris Male
>            Assignee: Chris Male
>             Fix For: 4.0
>         Attachments: LUCENE-3256.patch, LUCENE-3256.patch, LUCENE-3256.patch
> Lucene's CustomScoreQuery and Solr's BoostedQuery do essentially the same thing: they
boost the scores of Documents by the value from a ValueSource.  BoostedQuery does this in
a direct fashion, by accepting a ValueSource. CustomScoreQuery on the other hand, accepts
a series of ValueSourceQuerys.  ValueSourceQuery seems to do exactly the same thing as FunctionQuery.
> With Lucene's ValueSource being deprecated / removed, we need to resolve these dependencies
and simplify the code.
> Therefore I recommend we do the following things:
> - Move CustomScoreQuery (and CustomScoreProvider) to the new Queries module and change
it over to use FunctionQuerys instead of ValueSourceQuerys.  
> - Deprecate Solr's BoostedQuery in favour of the new CustomScoreQuery.  CSQ provides
a lot of support for customizing the scoring process.
> - Move and consolidate all tests of CSQ and BoostedQuery, to the Queries module and have
them test CSQ instead.

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