Hmmm, could you simply store a single-valued point field to use for sorting etc? It seems like the problem here is partly the same as for multiValued fields in general, which one should be used?
Best Erick On Mon, Jun 17, 2013 at 1:50 AM, William Bell <billnb...@gmail.com> wrote: > This simple feature of "sort=geodist() asc" is very powerful since it > enables us to move from SOLR 3 to SOLR 4 without rewriting all our queries. > > We also use boost=geodist() in some cases, and some bf/bq. > > bf=recip(geodist(),2,200,20)&sort=score > desc<http://localhost:8983/solr/select?fl=name,store,score&defType=dismax&q.alt=*:*&fq={!geofilt}&sfield=store&pt=45.15,-93.85&d=50&bf=recip(geodist(),2,200,20)&sort=score%20desc> > > OR > > boost=recip(geodist(),2,200,20)&sort=score > desc<http://localhost:8983/solr/select?fl=name,store,score&defType=edismax&q.alt=*:*&fq={!geofilt}&sfield=store&pt=45.15,-93.85&d=50&boost=recip%28geodist%28%29,2,200,20%29&sort=score%20desc> > > I know it specifically says it won't work for geohash multivalue points, > but what would it take to do it? > > > > > -- > Bill Bell > billnb...@gmail.com > cell 720-256-8076
