Mailing-List: contact lucene-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Lucene Developers List" <lucene-dev@jakarta.apache.org>
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <41E44166.1050103@apache.org>
Date: Tue, 11 Jan 2005 13:13:10 -0800
From: Doug Cutting <cutting@apache.org>
User-Agent: Mozilla Thunderbird 0.9 (X11/20041127)
MIME-Version: 1.0
To: Lucene Developers List <lucene-dev@jakarta.apache.org>
Subject: Re: How to proceed with Bug 31841 - MultiSearcher problems with
 Similarity.docFreq()
 ?
References: 
 <E3381E0825F1954D953A4E347017BB1C03032C44@reh001-1.REX001.ExchangeByRegister.com>
In-Reply-To: 
 <E3381E0825F1954D953A4E347017BB1C03032C44@reh001-1.REX001.ExchangeByRegister.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Chuck Williams wrote:
> As Wolf does, I hope a committer with deep knowledge of Lucene's design
> in this area will weigh in on the issue and help to resolve it.

The root of the bug is in MultiSearcher.search().  This should construct 
a Weight, weight the query, then score the now-weighted query.

Here's a potential way to fix it:

1. Replace all of the

    ... search(Query, ...)

methods in Searchable.java with

    ... search(Weight, ...)

methods.

2. Add search(Query, ...) convenience methods to Searcher.java which do 
something like:

   public ... search(Query query, ...) {
      return search(query.weight(this), ...);
   }

3. Update the search() methods in IndexSearcher, MultiSearcher and 
RemoteSearchable to operate on Weight's instead of queries.

Does that make sense?

Doug

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