Amir, CachedDistanceValueSource is indeed poorly named; I need to get renaming it on the TODO list; I've identified this before. Calculating the distance is computationally cheap enough to calculate for the X number of results (top-20-ish) you are returning in your search results to not bother trying to cache it, although I don't rule out caching it at some point.
On timing... know that the Lucene spatial module was committed in ~March, and there has been steady work lately on various components involved (Spatial4j, Lucene spatial module, Solr adapters). I *really* want to get this nailed down for Lucene/Solr 4. There is a big difference between simply having working code (that is only partially tested but seems to work), and addressing documentation, full testing, and consensus on the API between interested parties (e.g. Chris, Ryan, and me.). The last bit, consensus, is what bogs things down, in my experience. Specifically about the 1/distance thing... not sure when that'll happen, maybe in a couple weeks. Maybe. I created a JIRA issue so you can start watching it to be notified of progress: https://issues.apache.org/jira/browse/LUCENE-4208 ~ David ----- Author: http://www.packtpub.com/apache-solr-3-enterprise-search-server/book -- View this message in context: http://lucene.472066.n3.nabble.com/Spatial-Search-tp3623494p3994211.html Sent from the Lucene - Java Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
