You can try and use different execution mode (documented under type at the bottom here Elasticsearch Platform — Find real-time answers at scale | Elastic) to have it indexed instead of done in memory. As explained there, you will need to have the geo_point type mapping index the lat/lon as well in this case.
On Tuesday, January 31, 2012 at 6:39 PM, BeyondLimit wrote:
Hi there ,
Actually i have just stated using Elastic Search , and i have a
situation where in i have to search in the Boundary of lat/long .
When i have created the boundary and performed the search using java
code given below.client.prepareSearch() .setQuery(filteredQuery(textQuery("mappedfsn",
mapped), geoBoundingBoxFilter("location").topLeft(latt+
spreadOnLatitude, longii+ spreadOnLongitude).bottomRight(latt-
spreadOnLatitude, longii-
spreadOnLongitude))).setSize(NumRes).execute().actionGet();I found the search taking too much of time (200 mili sec on the Big
Server with 24gb of ram on it and i kept index on the Ram Disk too)
Now if i remove the boundingbox condition i get the result in no time
say 20 mili sec.Can any body help me on this.
Thanks in advance.
Regards
Prashant