GeoPoint mapping Option

Elastic Stack Elasticsearch
4

Hmmm I had missed your reply! Thanks!

I understand I should stick with in-memory. I still have a couples
questions for the sake of it:

  • When is the field loaded in memory? on-demand I presume. Is it loaded
    entirely (meaning first request might be slow and all subsequent geo
    constrained requests are fast)
  • How does one configure a mapping in the PUT mapping API. I mean the
    syntax is not clear from the website.

Best,

-stan

On Thursday, May 17, 2012 10:32:22 PM UTC+2, kimchy wrote:

First, you don't need to store the field. Second, by default, when the
lat_lon are not indexed, the values are loaded to memory and used for geo
calculations in memory (like checking bounding boxes, distances and the
like). For things that can use lat_lon that are indexed (like bounding
boxes), then you can configure the relevant geo filter to the the "checks"
instead of in memory, using the indexed lat_lon. Most times, the in memory
option is the one you want.

On Tue, May 15, 2012 at 12:03 PM, Stanislas Polu <polu.stanislas@gmail.com

wrote:

Hi,

There's very little information about the geopoint "lat_lon" indexation
option.
Can someone describe how queries are leveraging so that I can get a
better understanding of whether that would be helpful in my case?

  • there's also little information on how to pass an option to the
    geopoint mapping is this:

$ curl -XPUT 'http://localhost:9200/twitter/tweet/_mapping' -d '

{
"tweet" : {
"properties" : {
"message" : {"type" : "string", "store" : "yes", "lat_lon": "true"}

    }
}

}
'

Cheers,

-stan

--
Stanislas Polu
Mo: +33 6 83 71 90 04 | Tw: @spolu | http://teleportd.com | Realtime
Photo Search