I raised a JIRA, see:
https://issues.apache.org/jira/browse/SOLR-2829
Erick
On Thu, Oct 13, 2011 at 8:20 AM, Marc Tinnemeyer wrote:
> Thanks Erick
> In the meantime I checked against 3.3 and 3.1 but no difference there.
>
> Marc
>
> On 13.10.2011, at 14:00, Erick Erickson wrote:
>
>> Something's
Thanks Erick
In the meantime I checked against 3.3 and 3.1 but no difference there.
Marc
On 13.10.2011, at 14:00, Erick Erickson wrote:
> Something's not right here, I'll ask over on the
> dev list and we'll see what the reply is, you can
> monitor over there too if you'd like.
>
> Erick
>
> E
After looking at this a little more, it feels like
a caching issue. If I bounce the Solr server
between queries, it works just fine (I'm
on trunk now, but I think it's the same on 3.4).
Could you try that experiment a bit? Bounce
your Solr server between changing the field
and see if you get the c
Something's not right here, I'll ask over on the
dev list and we'll see what the reply is, you can
monitor over there too if you'd like.
Erick
Erick
On Wed, Oct 12, 2011 at 12:10 PM, Marc Tinnemeyer wrote:
> At first I thought so too. Here is a simple document.
>
>
>
> 1
At first I thought so too. Here is a simple document.
1
first
48.60,11.61
52.67,7.30
and here is the result that shouldn't be:
...
*:*
{!geofilt sfield=work pt=52.67,7.30 d=5}
...
52.67,7.30
1
first
48.60,11
Well, the simplest answer is that you're
putting the same information in home and
work. Or that they are close enough that
they are both within the radius.
Gotta see the raw data to generate a better
answer.
Best
Erick
On Wed, Oct 12, 2011 at 10:14 AM, Marc Tinnemeyer wrote:
> Hi everyone,
>
>
Hi everyone,
I am a bit troubled by a recent change in my configuration. I had to add two
additional fields of type "location" to the already existing one.
So the configuration looks like this:
Assuming that there are docs in the index having "home" set to: "50,20"
When I run a query like:
