Re: Cannot get ElasticSearch Config to Create Custom Analyzers

2015-05-15 Thread Jun Ohtani
Hi Wil, You should change `supplyhogText` to `default` in line 2, and delete last line. 2015-04-28 4:51 GMT+09:00 Wil Wade willm.w...@gmail.com: PasteBin of my attempted config: http://pastebin.com/175jeAMB ElasticSearch 1.5.2 So I want to have a custom default analyzer, but after days of

Re: Memory usage of the machine with ES is continuously increasing

2015-05-15 Thread Pradeep Reddy
Actually, the problem has appeared again, memory consumption was stable for couple of days, then it started increasing, env variable was only set for that particular session or something, I had to set it again by adding it to /etc/environment , but this doesn't have any affect anymore.. there

Modeling Objects That Have Many Properties

2015-05-15 Thread Peter Hodgman
Hello, I have a situation where I want to understand the best way to model this data in ES. I have the following data Object - Has Many - Properties where a Property - is a - Name (String), and a Value( one of - Boolean, Integer, Double, String, Long) and the Object is the container of

Re: Modeling Objects That Have Many Properties

2015-05-15 Thread Mark Walkom
You probably want to use parent/child instead, that way you don't have to update the entire document each time, just the child(ren). PS - We're moving to https://discuss.elastic.co/, please join us there for any future discussions! On 15 May 2015 at 22:52, Peter Hodgman peter.hodg...@gmail.com

Re: Remote access about Spark and Elasticsearch

2015-05-15 Thread Curt Kohler
I'm having the same problem today as well, although trying to access a server running in a AWS VPC (runs correctly with everything on my laptop). In my case, it appears to be trying to connect to the private IP address before failing over to the public one (which eventually works). Curt On

Re: Marvel showing unresponsive nodes but active data

2015-05-15 Thread Tristan Hammond
Mark, you're a lovely man. I finally got a spare few minutes to see what was up, and there was a 200s+ offset on the master. Not sure why our EC2 instance was not syncing time to correct that offset, as it's an AWS-built Ubuntu AMI. I corrected the offset on the master node and voilĂ ! Things