I tried following the examples, but I can't seem to make a
geo_distance (or any geo filter) work, using 0.10.0. Here's my steps,
after starting the search index:
The distance between the mentioned point is 114.94km, so you need to
broaden your search. A few pointers:
After indexing data, you will see the changes after 1 second (give or
take). If you test (i.e. execute fast consecutive curl requests, execute
refresh before the search).
On Fri, Sep 24, 2010 at 10:03 PM, Sean Bowman pico303@gmail.com wrote:
I tried following the examples, but I can't seem to make a
geo_distance (or any geo filter) work, using 0.10.0. Here's my steps,
after starting the search index:
Changing the range worked...finally! fireworks Thank you. I should
have checked that.
The sort idea is a good one too. Thanks for that reference. I can't
tell you how refreshing it is to have someone on a mailing list point
me at the correct documentation, rather than just tell me to read
everything on the entire site or type keywords into Google.
Just so you know, this is the example from your blog article and the
geo_distance filter doc on the web site. You might want to update the
documentation you've got up there and increase that "12km" to
"200km". There's also a typo in the sample JSON: no comma after the
"distance" : "12km" line. And while not technically a error, on the
sort documentation page, your query centers on [-40, 70], while your
examples were always [40, -70]. For consistency, you might want to
swap the negative there. Took me a second of wondering how I got
16000+km when you found 114km, before I realized the signs were
reversed.
This is only day two of using ElasticSearch, and I'm loving the
product. Outstanding work.
On Fri, Sep 24, 2010 at 11:37 PM, Sean Bowman pico303@gmail.com wrote:
Changing the range worked...finally! fireworks Thank you. I should
have checked that.
The sort idea is a good one too. Thanks for that reference. I can't
tell you how refreshing it is to have someone on a mailing list point
me at the correct documentation, rather than just tell me to read
everything on the entire site or type keywords into Google.
Just so you know, this is the example from your blog article and the
geo_distance filter doc on the web site. You might want to update the
documentation you've got up there and increase that "12km" to
"200km". There's also a typo in the sample JSON: no comma after the
"distance" : "12km" line. And while not technically a error, on the
sort documentation page, your query centers on [-40, 70], while your
examples were always [40, -70]. For consistency, you might want to
swap the negative there. Took me a second of wondering how I got
16000+km when you found 114km, before I realized the signs were
reversed.
This is only day two of using Elasticsearch, and I'm loving the
product. Outstanding work.
Unfortunately I can not get it working. I have tried many different approaches and it just doesn't work for me... I would really appreciate a full working example on 0.15.2, with mapping included.
I am new to ES and I would like to use it for a project I am working on, but I need the geo_distance search to work...
Apologies if I am missing something obvious. I have spent already a few days with this...
gist what you are doing, we can take it from there.
On Monday, March 28, 2011 at 1:34 AM, dcosta72 wrote:
Thanks Shay,
Unfortunately I can not get it working. I have tried many different
approaches and it just doesn't work for me... I would really appreciate a
full working example on 0.15.2, with mapping included.
I am new to ES and I would like to use it for a project I am working on, but
I need the geo_distance search to work...
Apologies if I am missing something obvious. I have spent already a few days
with this...
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.