Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Mime-Version: 1.0 (Apple Message framework v750)
In-Reply-To: <20060512111446.3kxu2k5frk8ws8sg@webmail.service.emory.edu>
References: <20060512111446.3kxu2k5frk8ws8sg@webmail.service.emory.edu>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <73A6FDD3-E17B-4CF9-921F-B7C74AE09850@ehatchersolutions.com>
Content-Transfer-Encoding: 7bit
From: Erik Hatcher <erik@ehatchersolutions.com>
Subject: Re: question about custom sort method
Date: Fri, 12 May 2006 12:38:06 -0400
To: java-user@lucene.apache.org

Yes, it does compute these distances for all the terms for the field  
specified, but only once (per IndexReader).  This is where the  
techniques Solr employs comes in real handy... warming up caches by  
running searches and sorts before putting a index into service.

	Erik


On May 12, 2006, at 11:14 AM, Urvashi Gadi wrote:

> I am looking at DistanceComparatorSource class (for csutom sorting)  
> and looks like it calculates the distance for each record in the  
> index and not just the records returned from search, making the  
> system very slow.
>
> Is my observation correct? Are there ways to optimize this process?
>
> Thanks,
> Urvashi
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org


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