Distance sorting with spatial filtering

The new spatial filtering (SOLR-1586) works great and is much faster than fq={!frange. However, I am having problems sorting by distance. If I try GET 'http://localhost:8983/solr/select/?q=*:*&sort=dist(2,latitude,longitude,0,0)+asc' I get an error: Error 400 can not sort on unindexed field: dist(

Re: Distance sorting with spatial filtering

Sep 1, 2010 at 18:43, Lance Norskog wrote: > Post your schema. > > On Mon, Aug 30, 2010 at 2:04 PM, Scott K wrote: >> The new spatial filtering (SOLR-1586) works great and is much faster >> than fq={!frange. However, I am having problems sorting by distance. >> If I t

Re: Distance sorting with spatial filtering

ctions may be on the list. But the _val_ trick is the > older one and, and you noted, still works. The _val_ trick sets the ranking > value to the output of the function, thus indirectly doing what sort= does. > > Lance > > Scott K wrote: >> >> I get the error on all fun

Re: Is there a way to fetch the complete list of data from a particular column in SOLR document?

But how do you know when the document actually makes it to solr, especially if you are using commitWithin and not explicitly calling commit. One solution is to have a status field in the database such as 0 - unindexed 1 - indexing 2 - committed / verified And have a separate process query solr fo

Re: Distance sorting with spatial filtering

) does not mention single-argument calls. This also fails http://localhost:8983/solr/select/?q=*:*&sort=sum(1,2)+asc http://localhost:8983/solr/select/?q=*:*&sort=sum(latitude,longitude)+asc > Scott K wrote: >> >> According to the documentation, sorting by function has

Re: Distance sorting with spatial filtering

n the Solr-1297 JIRA entry. Scott On Fri, Sep 10, 2010 at 01:40, Lance Norskog wrote: > Since no one has jumped in to give the right syntax- yeah, it's a bug. > Please file a JIRA. > > On Thu, Sep 9, 2010 at 9:44 PM, Scott K wrote: >> On Thu, Sep 9, 2010 at 21:00, Lance N

How do I get the solr error response as XML instead of HTML

solr errors come back as HTML instead of XM or JSON Is it possible to get the response to come back as XML or JSON, or at least something I could show to an end user? Is there a way to tell solr to ignore unparseable terms and still return a result, ideally with a warning so the end user doesn't

Re: NOT keyword - doesn't work with dismax?

I couldn't even get the bq= to work with negated queries, although with edismax, negated queries work with just q=-term Works: /solr/select?qt=edismax&q=-red Here is the failed attempt with dismax /solr/select?qt=dismax&rows=1&indent=true&q=-red&bq=*:*^0.001&echoParams=all&debugQuery=true { "r

Re: Spatial search in Solr 1.5

I just upgraded to a later version of the trunk and noticed my geofilter queries stopped working, apparently because the sfilt function was renamed to geofilt. I realize trunk is not stable, but other than looking at every change, is there an easy way to find changes that are not backward compatib

sort by price puts unknown prices first

When I sort by price ascending, documents with no price are listed first. I would like them listed last. I tried adding the sortMissingLast flag, even though it says it is only for strings, but it did not help. Why doesn't sortMissingLast work on non-strings? This seems like a very common issue, bu

Re: sort by price puts unknown prices first

On Wed, Mar 2, 2011 at 12:21, Chris Hostetter wrote: > historicly it has been because of a fundemental limitation in how the > Lucene FieldCache has historicly worked where the array backed FieldCaches > use the default numeric value (ie: 0) when docs have no value (but in the > case of Strings, t