lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Fernando Wasylyszyn <>
Subject Re: CustomScoreQueryWithSubqueries
Date Tue, 08 Feb 2011 11:34:38 GMT
Hi Doron. Thanks for your answer. Maybe the question seems simple, but I want to 
be sure about the procedure.
By the way, there is a chance, if the patch is really useful, that it could be 
"adapted" for other versions (in this case, lucene 3.0).

De: Doron Cohen <>
Enviado: martes, 8 de febrero, 2011 2:54:19
Asunto: Re: CustomScoreQueryWithSubqueries

Hi Fernando,
The wiki indeed relates mainly to trunk development.
For creating a 2.9 patch checkout code from 

As the wiki page says 
> Most development is done on the "trunk"
You can either use that, or, in order 

On Tue, Feb 8, 2011 at 4:56 AM, Fernando Wasylyszyn <> 

Robert: I'm trying to follow the steps that are mentioned in:
>in order to make a patch with my contribution. But, in the source code that I 
>get from:
>the class is missing and the only method 
>available to obtain a Scorer from a Weight object is 
>scorer(IndexReader.AtomicReaderContext, ScorerContext)
>I just checked and class Searcher still exists in Lucene 3.0.3. In which version 
>the trunk that I've checkout is based? The patch that I want to submit is based 
>on Lucene 2.9.1.
>Thanks in advance.
De: Robert Muir <>
>Enviado: miƩrcoles, 2 de febrero, 2011 16:52:58
>Asunto: Re: CustomScoreQueryWithSubqueries
>On Wed, Feb 2, 2011 at 2:37 PM, Fernando Wasylyszyn
><> wrote:
>> Hi everyone. My name is Fernando and I am a researcher and developer in the
>> R+D lab at Snoop Consulting S.R.L. in Argentina.
>> Based on the patch suggested in LUCENE-1608
>> ( and in the needs of one
>> of our customers, for who we are developing a customized search engine on
>> top of Lucene and Solr, we have developed the class
>> CustomScoreQueryWithSubqueries, which is a variation of CustomScoreQuery
>> that allows the use of arbitrary Query objects besides instances of
>> ValueSourceQuery, without the need of wrapping the arbitrary/ies query/ies
>>  with the QueryValueSource proposed in Jira, which has the disadvantage of
>> create an instance of an IndexSearcher in each invocation of the method
>> getValues(IndexReader).
>> If you think that this contribution can be useful for the Lucene community,
>> please let me know the steps in order to contribute.
>Hi Fernando: is
>still an open issue.
>If you have a better solution, please don't hesitate to upload a patch
>file to the issue!
>There are some more detailed instructions here:
>To unsubscribe, e-mail:
>For additional commands, e-mail:

View raw message