Re: Latitude - Lat, Longitude - lon

/ @elasticsearchfr / @scrutmydocs Le 7 juil. 2014 à 02:23, Olivier B obie...@gmail.com javascript: a écrit : Hi there, I understand a geo-point can be mapped based on two fields : lat, long. However my fields are name longitude and latitude. I'm using the river plugin for couchdb and I cannot

Latitude - Lat, Longitude - lon

Hi there, I understand a geo-point can be mapped based on two fields : lat, long. However my fields are name longitude and latitude. I'm using the river plugin for couchdb and I cannot really rename those fields before indexing. And those fields are part of an item in an array: items: [ {

IncompatibleClassChangeError[Implementing class]

Hey! I'm using Elasticsearch 1.1.1 on ubuntu on java 7: java version 1.7.0_55 OpenJDK Runtime Environment (IcedTea 2.4.7) (7u55-2.4.7-1ubuntu1) OpenJDK 64-Bit Server VM (build 24.51-b03, mixed mode) It's working perfectly. But, when I try to upgrade to 1.2.0, elasticsearch won't start:

Re: Filter aggregation and nested documents

Thanks you. OK, that's what I was fearing: the cache is loaded regardless of the filter condition. Which is a shame, even if we filter a lot, targeting only one document, we still need to fill up the cache! I will try to have a lot of RAM and see if I'm reaching a stable memory occupation and

Elasticsearch field cache always filled up and prevents other query to run.

Hi all, I set up an index containing 500.000 with million nested documents and I run big queries with a lot of aggregation. As expected this is using a LOT of memory and I easily have an OutOfMemory exception if a user perform a query for too many documents So I configured elasticsearch with