lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Male (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LUCENE-3256) Consolidate CustomScoreQuery, ValueSourceQuery and BoostedQuery
Date Thu, 30 Jun 2011 00:19:28 GMT

     [ https://issues.apache.org/jira/browse/LUCENE-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Male updated LUCENE-3256:
-------------------------------

    Attachment: LUCENE-3256.patch

New patch which incorporates Yonik's thoughts.  BoostedQuery is now a 1st class construct
and pushed to the module.  CustomScoreQuery now accepts arbitrary Querys as scorers.

Everything is jigged around a little again, since CSQ isn't specifically tied to FunctionQuery
(except on the test level).

Command is coming up.

This one is ready to go.

> Consolidate CustomScoreQuery, ValueSourceQuery and BoostedQuery 
> ----------------------------------------------------------------
>
>                 Key: LUCENE-3256
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3256
>             Project: Lucene - Java
>          Issue Type: Sub-task
>          Components: core/search
>            Reporter: 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: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message