Re: Full data in HDFS and Elasticsearch keeps the index pointer

Hi Costin, my query looks like this: POST _search { query: { filtered: { query: { match_all: {} }, filter: { bool: { must_not: [ { terms: {

Re: Full data in HDFS and Elasticsearch keeps the index pointer

And another one thing, I was misunderstanding, ES can't parallel work with another repository such like MySQL. I mean ES can't keep index pointer in itself, and index data in MySQL. All searching process must be done in ES. The only way improving performane seems like adding more machines,

Re: Integration of ElasticSearch with Cassandra

Hi asit, can you please share me your email id ? My company has been using cassandra but not efficiently so i am looking for similar impletation if they are successful so would like to know your experience On Wednesday, 27 August 2014 18:06:58 UTC+5:30, Asit Kaushik wrote: Hi All, We are

Re: What does it mean to store a field?

Hi Jorg/Nik, I tried the scenario like one with storing all fields and one without. So what i came across is -- The size of index is reduced as mentioned in preceding posts as well -- Search time for same query is slightly less with not storing the individual field -- But here I am getting an

Re: How to query with JSON when use Java API in ElasticSearch?

Hi Andrej, Thanks a lot for your kindly help. It's really give me a big progress. PS: I also found that QueryBuilders.wrapperQuery(String DSL) can do the same work. http://stackoverflow.com/questions/25859921/how-to-construct-querybuilder-from-json-dsl-when-using-java-api-in-elasticsearch

Re: What does it mean to store a field?

You must store the field for highlighting. Jörg On Tue, Sep 23, 2014 at 1:36 PM, Prashant Agrawal prashant.agra...@paladion.net wrote: Hi Jorg/Nik, I tried the scenario like one with storing all fields and one without. So what i came across is -- The size of index is reduced as mentioned

Re: Unnecessary Cache Eviction Explained

I opened issue #7836: https://github.com/elasticsearch/elasticsearch/issues/7836. On Monday, September 22, 2014 9:27:47 PM UTC-7, Otis Gospodnetic wrote: Hi, It sounds like every single ES deployment out there suffers from this, or am I missing something? Is there an ES issue where this

Re: Problem with word-separators in bool search with standard tokenizer

Hi Ankush, A few weeks ago I released an ElasticSearch plugin that allows you to override the default word boundary properties for Unicode characters as implemented by the StandardTokenizer algorithm. I had the same issue where I wanted to use the StandardTokenizer but override the word

Re: Why am I getting GC Warnings?

Thanks Mark, I thought so. But just in case I'll try to lower heap size from 16G to 10G to see if it will help or worsen the situation. On Monday, September 22, 2014 5:43:38 PM UTC-4, Mark Walkom wrote: I don't think it's anything you should be overly worried about as GC is normal. I am

Re: Unnecessary Cache Eviction Explained

Otis, from what I understand, the default size for the cache is unbounded, so cache eviction should not occur due to inconsistent range checks in the default case. -- Ivan On Mon, Sep 22, 2014 at 9:27 PM, Otis Gospodnetic otis.gospodne...@gmail.com wrote: Hi, It sounds like every single ES

Elasticsearch on EC2 R3 instances == trouble

Hi, Here is something worth sharing, I think. For Logsene http://sematext.com/logsene/, We've been trying out EC2 R3 instances (specifically r3.large) with Elasticsearch (1.1.x and 1.3.x including 1.3.2) with the latest Java 7 update 67. We tried this on Ubuntu 14.04 AMI, as well as Amazon

Re: Rollup data in ES

Hi, We aggregate outside of ES, in memory, and push in bulk. We could still roll up the data stored in ES later on if we wanted to, but reading from ES could get expensive. Otis -- Monitoring * Alerting * Anomaly Detection * Centralized Log Management Solr Elasticsearch Support *

Re: Unnecessary Cache Eviction Explained

Indeed, only instances with a value (greater than 0) specified for indices.fielddata.cache.size are affected. This is what triggers the use of Guava's eviction-based-on-size feature[1] Philippe [1]

Re: NPE in SignificanceHeuristicStreams.read while deserializing response (SearchResponse)

Thanks, Felipe. Problem reproduced and solution discovered. Please track https://github.com/elasticsearch/elasticsearch/issues/7840 for progress. On Monday, September 22, 2014 9:59:49 PM UTC+1, Felipe Hummel wrote: Hi Mark, I've created isolated mains for Java and Scala:

Re: NPE in SignificanceHeuristicStreams.read while deserializing response (SearchResponse)

Thanks Mark, glad I could help. In the meantime, is there any workaround to force the module to be load (without recompiling a ES .jar)? On Tue, Sep 23, 2014 at 1:49 PM, Mark Harwood mark.harw...@elasticsearch.com wrote: Thanks, Felipe. Problem reproduced and solution discovered. Please

Getting matched synonym

Hi, I would like to get the following result, but cant seem to find a solution: I have an index with a field which has f.i the value: laptop I have a synonym filter which maps laptop to notebook This all works fine, but what i would like is to show the user 'notebook' as autcomplete suggestion

Re: NPE in SignificanceHeuristicStreams.read while deserializing response (SearchResponse)

I feel grubby even suggesting this... https://gist.github.com/markharwood/0cecd5019dbd5c4e90fc but it looks to work. -- You received this message because you are subscribed to the Google Groups elasticsearch group. To unsubscribe from this group and stop receiving emails from it, send

Re: Elasticsearch _bulk periodically unavailable through Python API, but seems fine otherwise

Hello Henrik, My guess would be that the timeouts you are seeing in python are causing this - when the python client encounters a timeout, it retries the request, thinking something went wrong. Thus if your timeout is too small it can actually lead to spamming the cluster - when the python client

hits.hits array empty even thought total =1

I have a node app using the javascript api. even the the query returns a hit. I get the following response hits: { total: 1, max_score: 14.627042, hits: [] } how can the hits array be empty when the total shows 1.. If I run the query in sense I get the expected

Re: Elasticsearch version upgrade issue -- CorruptIndexException

This is a bug in lucene: https://issues.apache.org/jira/browse/LUCENE-5975 Sorry it took a while, thanks for reporting this! On Tue, Sep 9, 2014 at 7:18 PM, Wei ws...@groupon.com wrote: Hi All, I'm working on an ES upgrade from v0.20.5 to v1.2.1 I tested in a 2 node cluster, 3 indices, ~4

How many mappings is too many?

I did a quick search but couldn't find anything on this topic. We have a parent/child/grandchild relationship and our system has a dynamic number of parent mappings, but our child/grandchild mappings have a strict schema. This is because the data in the parent mapping is undefined and user