Re: ElasticSearch Version problem

Can we use jdbc river plugin for older versions of ES 0.90.3 ? On Sat, May 17, 2014 at 2:50 AM, joergpra...@gmail.com joergpra...@gmail.com wrote: Rivers did not change since ES 1.0.0 so I'm quite confident that https://github.com/richardwilly98/elasticsearch-river-mongodb 2.0.0 will run

Setting up indices (mappings, settings etc.)

Hello, I am struggeling to set up my indices correctly. I have a mappings file and a settings file that I would like to apply to my indices. Through trial and error I figured out that the below code works for me. However I am really not sure whether all steps that I take are necessary. Also

Re: ElasticSearch Version problem

Only latest ES 0.90.x (currently 0.90.13) is possible to support for JDBC river because of important bugfixes. I'd have to build a custom version of JDBC river for 0.90.13 Jörg On Sat, May 17, 2014 at 8:36 AM, Mukul Gupta mukulnit...@gmail.com wrote: Can we use jdbc river plugin for older

java client initialization

I am new to Elastic search. I wanted to know that i am using java client to access ES. Client client = new TransportClient().addTransportAddress(new InetSocketTransportAddress(127.0.0.1, 9300)); Should i initiated client everytime i execute query or just once? If i start it

Re: index update performance

Do anybody has any thoughts on below email points. Also, can anybody help me to locate any performance comparison between Databases (RDBMS) vs Lucene/ES index, for insert/update/delete feature. Thanks On Friday, May 16, 2014 7:44:56 PM UTC+5:30, Gaurav gupta wrote: Hi, We are exploring

Re: java client initialization

I think you need to only initialize in once on application (JVM) launch. You can alternatively use the JAVA client API :- Node node = nodeBuilder().node(); Client client = node.client(); Refer :-

Re: java client initialization

nodeBuilder or TransportClient both should be initialized once.right? -- 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 an email to

Re: ElasticSearch Version problem

Not an issue. I upgraded my ES to 1.1.0 anf mongo river to 2.0.0. Mongo river worked fine but jdbc river 1.1.0.1 is not working for me. I'm not able to import Mysql data into my index though I'm able to create mappings for it. But jdbc river is not importing any data into index. I followed this

Kibana 3.1.0 Upgrade Process..?

We've been using Kibana 3.0.0milestone5 for a while, and we have quite a few dashboards that are built with panels like the 'pie' and 'derive queries' panels. I was surprised to see the pie panel go away in 3.1.0. Is there any kind of an upgrade process or script we can run to upgrade our

How to create ES index with a mapping and data from Mysql ?

Hi, I'm using ES for creating an index with a mapping and data from Mysql. I'm able to create an empty idex along with mappings and settings but I'm not able to import data from Mysql into that index. I'm using https://github.com/jprante/elasticsearch-river-jdbc this plugin with ES 1.1.0

Re: ElasticSearch Version problem

For selecting an index/type, you can use curl -XPUT localhost:9200/_river/INDEX/_meta -d ' { type: jdbc, jdbc: { url: jdbc:mysql://localhost:3306/sapphire, driver: com.mysql.jdbc.Driver, user : root, password: root, sql : select * from flight, index : INDEX, type :

Re: Marvel monitoring on seperate cluster - connect timed out

Hi, Marvel 1.1.1 fixes the problem .. W dniu czwartek, 6 lutego 2014 14:33:07 UTC+1 użytkownik Boaz Leskes napisał: Weird. The missing info is standard ES and should be there independent of the OS (and solaris is supported, but not relevant here :)). Double checking - do you access the

Object interpolation in template queries

Hello, I'm interested in using query templates - http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/query-dsl-template-query.html - however for my purposes I was hoping ES treaded queries as simple strings for the purpose of mustache interpretation and I would to be able to

Re: Kibana 3.1.0 Upgrade Process..?

I don't think so, or haven't seen one. During the various v3 releases we had a few dashboards break and we just had to rebuild them manually. Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: ma...@campaignmonitor.com web: www.campaignmonitor.com On 18 May 2014 01:32, Matt

Problem with Boosting on Matched Nested Values

I have tried so many things I am starting to lose my mind. I have the following mapping for type 'product': https://gist.github.com/phirschybar/058d4fac11325887a451 I have the following query: https://gist.github.com/phirschybar/d3a2876ad367138e0b2d I am trying to return ALL products but