Re: question about custom sort method

Erik, You can reproduce OutOfMemory easily. I've attach test files - this is altered DistanceSortingTest example from LIA book. Also you can profile it and see caching of distances arrays. I'll try to investigate the problem, make patch to trunk version (probably non caching option) and get back

Re: question about custom sort method

On 7/17/06, Aleksey Serba <[EMAIL PROTECTED]> wrote: Yonik, thank you for your suggestion, we use solr codebase already :) To tell the truth, first time i thought this is solr caching problem ( i've modify SolrIndexSearcher to get lucene Searcher and search directly without any solr caching ) I

Re: question about custom sort method

Erik, I think Brian have the problem with continuous caching the same sorting values, i.e. he has a few points to calc distance from. In such case you can implement equals and hashCode methods based on point value and you'll have one cached comparator per different center point value. On 7/17/0

Re: question about custom sort method

There is a known issue with the DistanceComparatorSource in the "Lucene in Action" source code: Maybe this advice will help fix the issue you're having? Erik On Jul 17, 2006, at 9:54 AM, Aleksey Serba wrote:

Re: question about custom sort method

Hi! Peter, I have exactly the same situation described below. - I have DistanceComparatorSource to sort results by distance from specified spatial coordinates point. Point is different for each query. - I do not close Searcher after each query. - I get "java.lang.OutOfMemoryError: Java heap space

Re: question about custom sort method

FunctionQuery could also be used for this. http://incubator.apache.org/solr/docs/api/org/apache/solr/search/function/FunctionQuery.html -Yonik http://incubator.apache.org/solr Solr, the open-source Lucene search server On 5/17/06, Peter Keegan <[EMAIL PROTECTED]> wrote: Suppose I have a custom

Re: question about custom sort method

Suppose I have a custom sorting 'DocScoreComparator' for computing distances on each search hit from a specified coordinate (similar to the DistanceComparatorSource example in LIA). Assume that the 'specified coordinate' is different for each query. This means a new custom comparator must be creat

Re: question about custom sort method

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, 2

question about custom sort method

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, Urv