>> >>http://wiki.apache.org/solr/SolrAdaptersForLuceneSpatial4)
>>>> >>"q={!geofilt score=distance sfield=geo pt=54.729696,-98.525391 d=10}"
>>>> >>
>>>> >>assigns the distance/score based on the *closest* lat/long if the
>>&
gt;> >
>>> >>
>>> >>That's a reasonable default, but it's a bit arbitrary. Can I sort
>>>based
>>> >>on
>>> >>the *furthest* lat/long in the document? Or the average distance?
>>> >>
>>> >>Anyone know more about how this works and could give me some
>>>pointers?
>>> >
>>> >I considered briefly supporting the farthest distance but dismissed it
>>> as
>>> >I saw no real use-case. I didn't think of the average distance;
>>>that's
>>> >plausible. Any way, you're best bet is to dig into the code. The
>>> >relevant part is ShapeFieldCacheDistanceValueSource.
>>> >
>>> >FYI something to keep in mind:
>>> >https://issues.apache.org/jira/browse/LUCENE-4698
>>> >
>>> >~ David
>>> >
>>>
>>>
>>
>>
>> --
>> Bill Bell
>
>> billnbell@
>
>> cell 720-256-8076
>
>
>
>
>
>-
> Author:
>http://www.packtpub.com/apache-solr-3-enterprise-search-server/book
>--
>View this message in context:
>http://lucene.472066.n3.nabble.com/Distance-sort-on-a-multi-value-field-tp
>4084666p4085797.html
>Sent from the Solr - User mailing list archive at Nabble.com.
e know more about how this works and could give me some pointers?
>> >
>> >I considered briefly supporting the farthest distance but dismissed it
>> as
>> >I saw no real use-case. I didn't think of the average distance; that's
>> >plausible. Any way, you're best bet is to dig into the code. The
>> >relevant part is ShapeFieldCacheDistanceValueSource.
>> >
>> >FYI something to keep in mind:
>> >https://issues.apache.org/jira/browse/LUCENE-4698
>> >
>> >~ David
>> >
>>
>>
>
>
> --
> Bill Bell
> billnbell@
> cell 720-256-8076
-
Author: http://www.packtpub.com/apache-solr-3-enterprise-search-server/book
--
View this message in context:
http://lucene.472066.n3.nabble.com/Distance-sort-on-a-multi-value-field-tp4084666p4085797.html
Sent from the Solr - User mailing list archive at Nabble.com.
We have been using 2155 for over 6 months in production with over 2M hits
every 10 minutes. No OOM yet.
2155 seems great, and would this issue be any worse than 2155?
On Wed, Aug 14, 2013 at 4:08 PM, Jeff Wartes wrote:
>
> Hm, "Give me all the stores that only have branches in this area" migh
Hm, "Give me all the stores that only have branches in this area" might be
a plausible use case for farthest distance.
That's essentially a "contains" question though, so maybe that's already
supported? I guess it depends on how contains/intersects/etc handle
multi-values. I feel like multi-value
On 8/14/13 2:26 PM, "Jeff Wartes" wrote:
>
>I'm still pondering aggregate-type operations for scoring multi-valued
>fields (original thread: http://goo.gl/zOX53f ), and it occurred to me
>that distance-sort with SpatialRecursivePrefixTreeFieldType must be doing
>something like that.
It isn't.
I'm still pondering aggregate-type operations for scoring multi-valued
fields (original thread: http://goo.gl/zOX53f ), and it occurred to me
that distance-sort with SpatialRecursivePrefixTreeFieldType must be doing
something like that.
Somewhat surprisingly I don't see this in the documentation
