An Open Source implementation of Google Drive Realtime API

Hi all, I'd like to share an open-source project which implements nearly all features of the google drive realtime api. The *Google Drive Realtime API* https://developers.google.com/drive/realtime/ provides Google Docs–style instant collaboration. It lets multiple people edit the same data

Is there a method can trim meaning field before they returned when I search?

Dear all: I have a reasonable need, but I can't find how to deal with it on es official docs and books, is anyone know, please teach it to me! thank you! I have a large set of docs, which hold a lot of fields, such as a user info page. If I want analysis the gender distribution of all of

Re: New Logstash setup issue with iptables

Hi Lois, I had the exact same problem, the discovery is running on udp 54328 by default http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-zen.html, opening that port solved it for me. Hope it helps Linus On Thursday, July 3, 2014 9:16:31 PM UTC+2, Lois

Re: Is there a method can trim meaning field before they returned when I search?

Hello Magigo , Use the fields feature. You can tell which all fields you are interested in and it will return only those fields - http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-request-fields.html Thanks Vineeth On Sat, Jul 5, 2014 at 3:05 PM, 纪路

Re: Is there a method can trim meaning field before they returned when I search?

Also you need to start using this - http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-request-source-filtering.html Normal fields are depreciated. Thanks Vineeth On Sat, Jul 5, 2014 at 7:17 PM, vineeth mohan vm.vineethmo...@gmail.com wrote: Hello Magigo

Re: Stacked histograms of data from each event

Hello Tim and Eitan , There is a way we can do it , but am pretty sure its not the standard one. By adding different query string parameters , where each query have values from a different sensor. ​ I believe the standard method would be to do a aggregation on first level as term aggregation

Elasticsearch cluster re-start problem.

Hi, I have: ES: 1.1.0 version s3-gateway 2 data nodes we have started whole cluster. and now can not recover. Any solution around that? -- View this message in context: http://elasticsearch-users.115913.n3.nabble.com/Elasticsearch-cluster-re-start-problem-tp4059295.html Sent from the

Re: Option to disabled _index , _type , _id info in the response

You can try this plugin https://github.com/jprante/elasticsearch-arrayformat It reformats search results into a simple array of hits, throwing away _index, _type, _id Jörg On Sat, Jul 5, 2014 at 3:53 PM, vineeth mohan vm.vineethmo...@gmail.com wrote: Hello David , Well i have a case where

Re: Option to disabled _index , _type , _id info in the response

I see. The only thing I can see is to add another application layer or a REST plugin which does it. -- David ;-) Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 5 juil. 2014 à 15:53, vineeth mohan vm.vineethmo...@gmail.com a écrit : Hello David , Well i have a case where each

Re: Option to disabled _index , _type , _id info in the response

Yes , this is what i had in mind. Though its as simple as adding a extra layer , its kinda very useful when it comes to timeseries or small documents storage. Thanks Vineeth On Sat, Jul 5, 2014 at 7:33 PM, David Pilato da...@pilato.fr wrote: I see. The only thing I can see is to

Re: Stacked histograms of data from each event

THanks Vineeth, This is kinda what im trying to do. seperated my sensors into differnet types inside the same index. im currently facing 2 issues: 1. cannot find the right chart to present the measured values over time. best i can get is using the histogram yet this only shows max/min/mean

Re: ingest performance degrades sharply along with the documents having more fileds

Heya, I worked a bit on it, and 1.x (upcoming 1.3) has some significant perf improvements now for this case (including improvements Lucene wise, that are for now in ES, but will be in Lucene next version). Those include: 6648: https://github.com/elasticsearch/elasticsearch/pull/6648 6714:

is TTL config change in 1.2 ?

Hi I used to create index with a TTL like this curl -X POST http://localhost:9200/index_test -d '{ mappings:{ document:{ _ttl:{ enable:true }, properties:{ text:{ type:string } } } }, settings:{ number_of_replicas:1,

Re: is TTL config change in 1.2 ?

sorry typo: enable vs enabled On Saturday, July 5, 2014 5:59:31 PM UTC+2, seb wrote: Hi I used to create index with a TTL like this curl -X POST http://localhost:9200/index_test -d '{ mappings:{ document:{ _ttl:{ enable:true }, properties:{

Re: Setting replication to async

The default setting of Elasticsearch is replication mode sync for good reason, this ensures the replica quorum (which is often determined as eventual consistency but this is really something more because it describes properties of the last-seen value for update). Replication setting of async does

Kibana Terms Graph Not Working

I'm stumped. I have a field called ExceptionMessage. Here is a sample message: System.Exception No pricing configuration found for ItemCode IA636 When I created a terms count panel on ExceptionMessage, Kibana is counting each word in the message as an ExceptionMessage. Example,

Re: Elasticsearch cluster re-start problem.

Can you elaborate, do you mean recover the indexes? What do your logs show? Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: ma...@campaignmonitor.com web: www.campaignmonitor.com On 6 July 2014 00:01, Tarun Jangra ta...@izap.in wrote: Hi, I have: ES: 1.1.0 version

excessive merging/small segment sizes

We have a situation where one of the four nodes in our cluster seems to get caught up endlessly merging. However it seems to be high CPU activity and not I/O constrainted. I have enabled the IndexWriter info stream logs, and often times it seems to do merges of quite small segments (100KB)

Re: Is there a method can trim meaning field before they returned when I search?

Hi Vineeth: Thank for your answer, source filtering is very useful. About fields, it seems that its function is different from source filtering, it can prevent additional fields from load in the system before search, is it? The depreciated function is partial, not fields, is my opinion right?