Yeah we use this in production. Yonik: WHat are the performance
implication with doing this? Will the fq be cached?
On Sat, Jun 25, 2011 at 7:27 AM, Yonik Seeley
<yo...@lucidimagination.com> wrote:
> On Sat, Jun 25, 2011 at 5:56 AM, marthinal <jm.rodriguez.ve...@gmail.com>
> wrote:
>>> sfield, pt and d can all be specified directly in the spatial
>>> functions/filters too, and that will override the global params.
>>>
>>> Unfortunately one must currently use lucene query syntax to do an OR.
>>> It just makes it look a bit messier.
>>>
>>> q=_query_:"{!geofilt}" _query:"{!geofilt sfield=location_2}"
>>>
>>> -Yonik
>>> http://www.lucidimagination.com
>>>
>>
>> @Yonik it seems to work like this, i triyed houndreds of other possibilities
>> without success:
>>
>> q={!geofilt sfield=location_1 pt=36.62,-6.23 d=50}&fq={!geofilt
>> sfield=location_2 pt=40.51,-5.91 d=500}
>
> Ah, right. I had thought you wanted docs that matched either geofilt
> (hence OR), not docs that only matched both.
>
> -Yonik
> http://www.lucidimagination.com
>
--
Bill Bell
billnb...@gmail.com
cell 720-256-8076
