It is precisely this limitation which triggered me to develop a grid indexing
approach using Geohashes: https://issues.apache.org/jira/browse/SOLR-2155
This patch requires a Solr trunk release.
If you have a small number of distinct points in total, and you only need
filtering, then the geohash
Will it be possible to do spatial searches on multi-valued spatial
fields soon?
I have a latlon field (point) that is multi-valued and don't know how to
search against it
such that the lats and lons match correctly - since they are split apart.
e.g. I have a document with 10 point/latlon valu
Yonik Seeley-2-2 wrote:
>
> On Sat, Jun 25, 2011 at 5:56 AM, marthinal
> 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
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
wrote:
> On Sat, Jun 25, 2011 at 5:56 AM, marthinal
> wrote:
>>> sfield, pt and d can all be specified directly in the spatial
>>> fu
On Sat, Jun 25, 2011 at 5:56 AM, marthinal 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.
Yonik Seeley-2-2 wrote:
>
> On Fri, Jun 24, 2011 at 2:11 PM, marthinal
> wrote:
>>
>> Yonik Seeley-2-2 wrote:
>>>
>>> On Tue, Sep 21, 2010 at 12:12 PM, dan sutton
>>>
>>> wrote:
I was looking at the LatLonType and how it might represent m
On Fri, Jun 24, 2011 at 2:11 PM, marthinal wrote:
>
> Yonik Seeley-2-2 wrote:
>>
>> On Tue, Sep 21, 2010 at 12:12 PM, dan sutton
>> wrote:
>>> I was looking at the LatLonType and how it might represent multiple
>>> lon/lat
>>> values ... it looks to me like the lat would go
Yonik Seeley-2-2 wrote:
>
> On Tue, Sep 21, 2010 at 12:12 PM, dan sutton
> wrote:
>> I was looking at the LatLonType and how it might represent multiple
>> lon/lat
>> values ... it looks to me like the lat would go in
>> {latlongfield}_0_LatLon
>> and the long in {latlongfi
On Tue, Sep 21, 2010 at 12:12 PM, dan sutton wrote:
> I was looking at the LatLonType and how it might represent multiple lon/lat
> values ... it looks to me like the lat would go in {latlongfield}_0_LatLon
> and the long in {latlongfield}_1_LatLon ... how then if we have multiple
> lat/long point