Re: Availability for the ElasticSearch 2 streaming connector

2016-02-18 Thread Zach Cox
Awesome, thanks Suneel. :D I made the changes to support our use case, which needed flatMap behavior (index 2 docs, or zero docs, per incoming element) instead of map, and we also need to make either IndexRequest or UpdateRequest depending on the element. -Zach On Thu, Feb 18, 2016 at 2:06 AM S

Re: Availability for the ElasticSearch 2 streaming connector

2016-02-18 Thread Suneel Marthi
Thanks Zach, I have a few minor changes too locally; I'll push a PR out tomorrow that has ur changes too. On Wed, Feb 17, 2016 at 5:13 PM, Zach Cox wrote: > I recently did exactly what Robert described: I copied the code from this > (closed) PR https://github.com/apache/flink/pull/1479, modified

Re: Availability for the ElasticSearch 2 streaming connector

2016-02-17 Thread Zach Cox
I recently did exactly what Robert described: I copied the code from this (closed) PR https://github.com/apache/flink/pull/1479, modified it a bit, and just included it in my own project that uses the Elasticsearch 2 java api. Seems to work well. Here are the files so you can do the same: https://

Re: Availability for the ElasticSearch 2 streaming connector

2016-02-17 Thread Suneel Marthi
Hey I missed this thread, sorry about that. I have a basic connector working with ES 2.0 which I can push out. Its not optimized yet and I don't have the time to look at it, if someone would like to take it over go ahead I can send a PR. On Wed, Feb 17, 2016 at 4:57 PM, Robert Metzger wrote: >

Re: Availability for the ElasticSearch 2 streaming connector

2016-02-17 Thread Robert Metzger
Hi Mihail, It seems that nobody is actively working on the elasticsearch2 connector right now. The 1.0.0 release is already feature frozen, only bug fixes or (some) pending pull requests go in. What you can always do is copy the code from our current elasticsearch connector, set the dependency to