You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@storm.apache.org by Tech Id <te...@gmail.com> on 2016/03/19 03:45:17 UTC

external/storm-elasticsearch - upgrade requested

Hi,

I see that the version of elastic-search used
in external/storm-elasticsearch/pom.xml is quite old (1.6.0) while the
latest elastic-search is 2.2.0

2.x version is not compatible with 1.x version of elastic-search and so I
request you to upgrade.

Also, current storm-elasticsearch uses TransportClient of elastic-search
but does not expose many of the useful options in the TransportClient (like
routing).

Request you to expose them to the users too.


Thanks
Tid

Re: external/storm-elasticsearch - upgrade requested

Posted by Julien Nioche <li...@gmail.com>.
FYI there is an ES module in StormCrawler [
https://github.com/DigitalPebble/storm-crawler/tree/master/external/elasticsearch],
its components are quite specific to storm-crawler apart from the
MetricsComsumer
<https://github.com/DigitalPebble/storm-crawler/tree/master/external/elasticsearch/src/main/java/com/digitalpebble/storm/crawler/elasticsearch/metrics>
which
can be used with any Storm topology e.g. to build graphs with Kibana. To my
knowledge this is not available in ES-Hadoop nor storm-elasticsearch. There
is a few dependencies to objects from storm-crawler but these should be
easy to circumvent if you wanted to piggyback the code.





On 1 April 2016 at 19:32, Lakshmanan Muthuraman <la...@tokbox.com>
wrote:

> 1."ES-Hadoop also provides a good support of time-based index-rolling
> which is great for logging-type use-cases."
> 2. If trident is not needed, ES-Hadoop is simple enough to use.
>
> The above is a big usecase for us that we are able to accomplish with
> ElasticSearch-Hadoop
>
>
> On Wed, Mar 30, 2016 at 11:50 AM, Aaron.Dossett <Aa...@target.com>
> wrote:
>
>> Size of cluster is TBD, but we ultimately want to ingest tens of millions
>> of events per minute.
>>
>> On Mar 30, 2016, at 1:31 PM, Tech Id <te...@gmail.com> wrote:
>>
>>
>> Hey Aaron,
>>
>> Do you have a target throughput that you want to achieve through ES-Bolt ?
>> How many storm machines you plan to run your topology on?
>>
>> Thanks
>>
>>
>> On Wed, Mar 30, 2016 at 10:53 AM, Aaron.Dossett <Aaron.Dossett@target.com
>> > wrote:
>>
>>> In setting up a storm -> ES topology today I ran across that same fact.
>>> The EsIndexBolt is also synchronous mode only, with no option for asynch.
>>> This week I’ll evaluate adding batching/async to storm-elasticsearch or
>>> switching to ES-hadoop for my use use cases.
>>>
>>> From: Tech Id <te...@gmail.com>
>>> Reply-To: "user@storm.apache.org" <us...@storm.apache.org>
>>> Date: Wednesday, March 30, 2016 at 10:24 AM
>>> To: "user@storm.apache.org" <us...@storm.apache.org>
>>> Subject: Re: external/storm-elasticsearch - upgrade requested
>>>
>>> One thing I see in favor of the elasticsearch-hadoop is that it provides
>>> batching without Trident.
>>>
>>
>>
>


-- 

*Open Source Solutions for Text Engineering*

http://www.digitalpebble.com
http://digitalpebble.blogspot.com/
#digitalpebble <http://twitter.com/digitalpebble>

Re: external/storm-elasticsearch - upgrade requested

Posted by Lakshmanan Muthuraman <la...@tokbox.com>.
1."ES-Hadoop also provides a good support of time-based index-rolling which
is great for logging-type use-cases."
2. If trident is not needed, ES-Hadoop is simple enough to use.

The above is a big usecase for us that we are able to accomplish with
ElasticSearch-Hadoop


On Wed, Mar 30, 2016 at 11:50 AM, Aaron.Dossett <Aa...@target.com>
wrote:

> Size of cluster is TBD, but we ultimately want to ingest tens of millions
> of events per minute.
>
> On Mar 30, 2016, at 1:31 PM, Tech Id <te...@gmail.com> wrote:
>
>
> Hey Aaron,
>
> Do you have a target throughput that you want to achieve through ES-Bolt ?
> How many storm machines you plan to run your topology on?
>
> Thanks
>
>
> On Wed, Mar 30, 2016 at 10:53 AM, Aaron.Dossett <Aa...@target.com>
> wrote:
>
>> In setting up a storm -> ES topology today I ran across that same fact.
>> The EsIndexBolt is also synchronous mode only, with no option for asynch.
>> This week I’ll evaluate adding batching/async to storm-elasticsearch or
>> switching to ES-hadoop for my use use cases.
>>
>> From: Tech Id <te...@gmail.com>
>> Reply-To: "user@storm.apache.org" <us...@storm.apache.org>
>> Date: Wednesday, March 30, 2016 at 10:24 AM
>> To: "user@storm.apache.org" <us...@storm.apache.org>
>> Subject: Re: external/storm-elasticsearch - upgrade requested
>>
>> One thing I see in favor of the elasticsearch-hadoop is that it provides
>> batching without Trident.
>>
>
>

Re: external/storm-elasticsearch - upgrade requested

Posted by "Aaron.Dossett" <Aa...@target.com>.
Size of cluster is TBD, but we ultimately want to ingest tens of millions of events per minute.

On Mar 30, 2016, at 1:31 PM, Tech Id <te...@gmail.com>> wrote:


Hey Aaron,

Do you have a target throughput that you want to achieve through ES-Bolt ?
How many storm machines you plan to run your topology on?

Thanks


On Wed, Mar 30, 2016 at 10:53 AM, Aaron.Dossett <Aa...@target.com>> wrote:
In setting up a storm -> ES topology today I ran across that same fact.  The EsIndexBolt is also synchronous mode only, with no option for asynch. This week I'll evaluate adding batching/async to storm-elasticsearch or switching to ES-hadoop for my use use cases.

From: Tech Id <te...@gmail.com>>
Reply-To: "user@storm.apache.org<ma...@storm.apache.org>" <us...@storm.apache.org>>
Date: Wednesday, March 30, 2016 at 10:24 AM
To: "user@storm.apache.org<ma...@storm.apache.org>" <us...@storm.apache.org>>
Subject: Re: external/storm-elasticsearch - upgrade requested

One thing I see in favor of the elasticsearch-hadoop is that it provides batching without Trident.

Re: external/storm-elasticsearch - upgrade requested

Posted by Tech Id <te...@gmail.com>.
Hey Aaron,

Do you have a target throughput that you want to achieve through ES-Bolt ?
How many storm machines you plan to run your topology on?

Thanks


On Wed, Mar 30, 2016 at 10:53 AM, Aaron.Dossett <Aa...@target.com>
wrote:

> In setting up a storm -> ES topology today I ran across that same fact.
> The EsIndexBolt is also synchronous mode only, with no option for asynch.
> This week I’ll evaluate adding batching/async to storm-elasticsearch or
> switching to ES-hadoop for my use use cases.
>
> From: Tech Id <te...@gmail.com>
> Reply-To: "user@storm.apache.org" <us...@storm.apache.org>
> Date: Wednesday, March 30, 2016 at 10:24 AM
> To: "user@storm.apache.org" <us...@storm.apache.org>
> Subject: Re: external/storm-elasticsearch - upgrade requested
>
> One thing I see in favor of the elasticsearch-hadoop is that it provides
> batching without Trident.
>

Re: external/storm-elasticsearch - upgrade requested

Posted by "Aaron.Dossett" <Aa...@target.com>.
In setting up a storm -> ES topology today I ran across that same fact.  The EsIndexBolt is also synchronous mode only, with no option for asynch. This week I'll evaluate adding batching/async to storm-elasticsearch or switching to ES-hadoop for my use use cases.

From: Tech Id <te...@gmail.com>>
Reply-To: "user@storm.apache.org<ma...@storm.apache.org>" <us...@storm.apache.org>>
Date: Wednesday, March 30, 2016 at 10:24 AM
To: "user@storm.apache.org<ma...@storm.apache.org>" <us...@storm.apache.org>>
Subject: Re: external/storm-elasticsearch - upgrade requested

One thing I see in favor of the elasticsearch-hadoop is that it provides batching without Trident.

Re: external/storm-elasticsearch - upgrade requested

Posted by Tech Id <te...@gmail.com>.
I think elasticsearch-hadoop has a good number of options to tune and those
are documented well too.
(See
https://www.elastic.co/guide/en/elasticsearch/hadoop/current/configuration.html
)

One thing I see in favor of the elasticsearch-hadoop is that it provides
batching without Trident.
This could be a very good thing for someone not using Trident.

ES-Hadoop also does a node discovery of all the ES-nodes and then writes
data to only primary shards (which avoids a jump from replica-shards to
primary-shards).

ES-Hadoop supported routing until 2.x version of ES and there is a bug to
make it work in 2.x version as well.

ES-Hadoop also provides a good support of time-based index-rolling which is
great for logging-type use-cases.

Some more features include authentication, SSL, proxy etc.

I haven't looked much closely into storm-elasticsearch to see if it
provides the same functionality.

We should compare the above features and run some performance tests to
compare the two.

Disclaimer: I am just a simple user of ES-Hadoop and not associated with it
in any way. Would love to switch to some other bolt if its better or more
performant.


On Sat, Mar 26, 2016 at 8:11 PM, Jungtaek Lim <ka...@gmail.com> wrote:

> Lakshmanan,
>
> We looked over elasticsearch-hadoop when we adopted storm-elasticsearch,
> and elasticsearch-hadoop has only basic feature at that time.
> (No trident implementation)
> Please refer https://github.com/apache/storm/pull/573 to track our
> discussion on this module.
>
> Thanks!
> Jungtaek Lim (HeartSaVioR)
>
> 2016년 3월 27일 (일) 오전 3:12, Lakshmanan Muthuraman <la...@tokbox.com>님이
> 작성:
>
>> We have been using elasticsearch-hadoop to write to ElasticSearch from
>> Storm. It looks good so far. Any thoughts on adopting ElasticSearch Hadoop
>> as  part of Storm external rather than trying to write and maintain our own
>> bolt in Storm Project.
>>
>> Any thoughts?
>>
>> On Tue, Mar 22, 2016 at 2:19 PM, Aaron.Dossett <Aa...@target.com>
>> wrote:
>>
>>> No, we hadn’t looked at that, but once we are streaming into elastic at
>>> scale (not there yet) I would be interested to compare.
>>>
>>> From: Tech Id <te...@gmail.com>
>>> Reply-To: "user@storm.apache.org" <us...@storm.apache.org>
>>> Date: Monday, March 21, 2016 at 1:21 PM
>>> To: "user@storm.apache.org" <us...@storm.apache.org>
>>> Subject: Re: external/storm-elasticsearch - upgrade requested
>>>
>>> Thanks Aaron,
>>>
>>> Did you have a chance to compare the elasticsearch-hadoop (
>>> https://www.elastic.co/guide/en/elasticsearch/hadoop/current/storm.html)
>>> with the storm-elasticsearch (
>>> https://github.com/apache/storm/tree/master/external/storm-elasticsearch)
>>> ?
>>>
>>> Former uses REST client while the latter uses TransportClient.
>>>
>>> It would be interesting to know some performance numbers between them.
>>>
>>> Thanks !
>>>
>>> On Mon, Mar 21, 2016 at 5:40 AM, Aaron.Dossett <Aaron.Dossett@target.com
>>> > wrote:
>>>
>>>> Hi,
>>>>
>>>> The best way to make feature requests like this is via the Apache Jira.
>>>> (https://issues.apache.org/jira/browse/STORM/)
>>>>
>>>> As it happens, my team (at Target) has adapted the elastic search bolt
>>>> for 2.X and we are using it in production.  We opened a JIRA (
>>>> https://issues.apache.org/jira/browse/STORM-1475) to track that and
>>>> contribute our change back to the project.  We’re cleaning a couple of
>>>> things up right now, but I’m hopeful we will contribute it back soon.
>>>>
>>>> Your second request could be a nice feature enhancement, can you open a
>>>> JIRA for it? In my experience, these external bolts are a really nice way
>>>> to get involved with the project as well. You could try adding a couple of
>>>> features and contributing those.
>>>>
>>>> Thanks!
>>>>
>>>> From: Tech Id <te...@gmail.com>
>>>> Reply-To: "user@storm.apache.org" <us...@storm.apache.org>
>>>> Date: Friday, March 18, 2016 at 9:45 PM
>>>> To: "user@storm.apache.org" <us...@storm.apache.org>
>>>> Subject: external/storm-elasticsearch - upgrade requested
>>>>
>>>> Hi,
>>>>
>>>> I see that the version of elastic-search used
>>>> in external/storm-elasticsearch/pom.xml is quite old (1.6.0) while the
>>>> latest elastic-search is 2.2.0
>>>>
>>>> 2.x version is not compatible with 1.x version of elastic-search and so
>>>> I request you to upgrade.
>>>>
>>>> Also, current storm-elasticsearch uses TransportClient of
>>>> elastic-search but does not expose many of the useful options in the
>>>> TransportClient (like routing).
>>>>
>>>> Request you to expose them to the users too.
>>>>
>>>>
>>>> Thanks
>>>> Tid
>>>>
>>>
>>>
>>

Re: external/storm-elasticsearch - upgrade requested

Posted by Jungtaek Lim <ka...@gmail.com>.
Lakshmanan,

We looked over elasticsearch-hadoop when we adopted storm-elasticsearch,
and elasticsearch-hadoop has only basic feature at that time.
(No trident implementation)
Please refer https://github.com/apache/storm/pull/573 to track our
discussion on this module.

Thanks!
Jungtaek Lim (HeartSaVioR)

2016년 3월 27일 (일) 오전 3:12, Lakshmanan Muthuraman <la...@tokbox.com>님이
작성:

> We have been using elasticsearch-hadoop to write to ElasticSearch from
> Storm. It looks good so far. Any thoughts on adopting ElasticSearch Hadoop
> as  part of Storm external rather than trying to write and maintain our own
> bolt in Storm Project.
>
> Any thoughts?
>
> On Tue, Mar 22, 2016 at 2:19 PM, Aaron.Dossett <Aa...@target.com>
> wrote:
>
>> No, we hadn’t looked at that, but once we are streaming into elastic at
>> scale (not there yet) I would be interested to compare.
>>
>> From: Tech Id <te...@gmail.com>
>> Reply-To: "user@storm.apache.org" <us...@storm.apache.org>
>> Date: Monday, March 21, 2016 at 1:21 PM
>> To: "user@storm.apache.org" <us...@storm.apache.org>
>> Subject: Re: external/storm-elasticsearch - upgrade requested
>>
>> Thanks Aaron,
>>
>> Did you have a chance to compare the elasticsearch-hadoop (
>> https://www.elastic.co/guide/en/elasticsearch/hadoop/current/storm.html)
>> with the storm-elasticsearch (
>> https://github.com/apache/storm/tree/master/external/storm-elasticsearch)
>> ?
>>
>> Former uses REST client while the latter uses TransportClient.
>>
>> It would be interesting to know some performance numbers between them.
>>
>> Thanks !
>>
>> On Mon, Mar 21, 2016 at 5:40 AM, Aaron.Dossett <Aa...@target.com>
>> wrote:
>>
>>> Hi,
>>>
>>> The best way to make feature requests like this is via the Apache Jira. (
>>> https://issues.apache.org/jira/browse/STORM/)
>>>
>>> As it happens, my team (at Target) has adapted the elastic search bolt
>>> for 2.X and we are using it in production.  We opened a JIRA (
>>> https://issues.apache.org/jira/browse/STORM-1475) to track that and
>>> contribute our change back to the project.  We’re cleaning a couple of
>>> things up right now, but I’m hopeful we will contribute it back soon.
>>>
>>> Your second request could be a nice feature enhancement, can you open a
>>> JIRA for it? In my experience, these external bolts are a really nice way
>>> to get involved with the project as well. You could try adding a couple of
>>> features and contributing those.
>>>
>>> Thanks!
>>>
>>> From: Tech Id <te...@gmail.com>
>>> Reply-To: "user@storm.apache.org" <us...@storm.apache.org>
>>> Date: Friday, March 18, 2016 at 9:45 PM
>>> To: "user@storm.apache.org" <us...@storm.apache.org>
>>> Subject: external/storm-elasticsearch - upgrade requested
>>>
>>> Hi,
>>>
>>> I see that the version of elastic-search used
>>> in external/storm-elasticsearch/pom.xml is quite old (1.6.0) while the
>>> latest elastic-search is 2.2.0
>>>
>>> 2.x version is not compatible with 1.x version of elastic-search and so
>>> I request you to upgrade.
>>>
>>> Also, current storm-elasticsearch uses TransportClient of elastic-search
>>> but does not expose many of the useful options in the TransportClient (like
>>> routing).
>>>
>>> Request you to expose them to the users too.
>>>
>>>
>>> Thanks
>>> Tid
>>>
>>
>>
>

Re: external/storm-elasticsearch - upgrade requested

Posted by Lakshmanan Muthuraman <la...@tokbox.com>.
We have been using elasticsearch-hadoop to write to ElasticSearch from
Storm. It looks good so far. Any thoughts on adopting ElasticSearch Hadoop
as  part of Storm external rather than trying to write and maintain our own
bolt in Storm Project.

Any thoughts?

On Tue, Mar 22, 2016 at 2:19 PM, Aaron.Dossett <Aa...@target.com>
wrote:

> No, we hadn’t looked at that, but once we are streaming into elastic at
> scale (not there yet) I would be interested to compare.
>
> From: Tech Id <te...@gmail.com>
> Reply-To: "user@storm.apache.org" <us...@storm.apache.org>
> Date: Monday, March 21, 2016 at 1:21 PM
> To: "user@storm.apache.org" <us...@storm.apache.org>
> Subject: Re: external/storm-elasticsearch - upgrade requested
>
> Thanks Aaron,
>
> Did you have a chance to compare the elasticsearch-hadoop (
> https://www.elastic.co/guide/en/elasticsearch/hadoop/current/storm.html)
> with the storm-elasticsearch (
> https://github.com/apache/storm/tree/master/external/storm-elasticsearch)
> ?
>
> Former uses REST client while the latter uses TransportClient.
>
> It would be interesting to know some performance numbers between them.
>
> Thanks !
>
> On Mon, Mar 21, 2016 at 5:40 AM, Aaron.Dossett <Aa...@target.com>
> wrote:
>
>> Hi,
>>
>> The best way to make feature requests like this is via the Apache Jira. (
>> https://issues.apache.org/jira/browse/STORM/)
>>
>> As it happens, my team (at Target) has adapted the elastic search bolt
>> for 2.X and we are using it in production.  We opened a JIRA (
>> https://issues.apache.org/jira/browse/STORM-1475) to track that and
>> contribute our change back to the project.  We’re cleaning a couple of
>> things up right now, but I’m hopeful we will contribute it back soon.
>>
>> Your second request could be a nice feature enhancement, can you open a
>> JIRA for it? In my experience, these external bolts are a really nice way
>> to get involved with the project as well. You could try adding a couple of
>> features and contributing those.
>>
>> Thanks!
>>
>> From: Tech Id <te...@gmail.com>
>> Reply-To: "user@storm.apache.org" <us...@storm.apache.org>
>> Date: Friday, March 18, 2016 at 9:45 PM
>> To: "user@storm.apache.org" <us...@storm.apache.org>
>> Subject: external/storm-elasticsearch - upgrade requested
>>
>> Hi,
>>
>> I see that the version of elastic-search used
>> in external/storm-elasticsearch/pom.xml is quite old (1.6.0) while the
>> latest elastic-search is 2.2.0
>>
>> 2.x version is not compatible with 1.x version of elastic-search and so I
>> request you to upgrade.
>>
>> Also, current storm-elasticsearch uses TransportClient of elastic-search
>> but does not expose many of the useful options in the TransportClient (like
>> routing).
>>
>> Request you to expose them to the users too.
>>
>>
>> Thanks
>> Tid
>>
>
>

Re: external/storm-elasticsearch - upgrade requested

Posted by "Aaron.Dossett" <Aa...@target.com>.
No, we hadn't looked at that, but once we are streaming into elastic at scale (not there yet) I would be interested to compare.

From: Tech Id <te...@gmail.com>>
Reply-To: "user@storm.apache.org<ma...@storm.apache.org>" <us...@storm.apache.org>>
Date: Monday, March 21, 2016 at 1:21 PM
To: "user@storm.apache.org<ma...@storm.apache.org>" <us...@storm.apache.org>>
Subject: Re: external/storm-elasticsearch - upgrade requested

Thanks Aaron,

Did you have a chance to compare the elasticsearch-hadoop (https://www.elastic.co/guide/en/elasticsearch/hadoop/current/storm.html) with the storm-elasticsearch (https://github.com/apache/storm/tree/master/external/storm-elasticsearch) ?

Former uses REST client while the latter uses TransportClient.

It would be interesting to know some performance numbers between them.

Thanks !

On Mon, Mar 21, 2016 at 5:40 AM, Aaron.Dossett <Aa...@target.com>> wrote:
Hi,

The best way to make feature requests like this is via the Apache Jira. (https://issues.apache.org/jira/browse/STORM/)

As it happens, my team (at Target) has adapted the elastic search bolt for 2.X and we are using it in production.  We opened a JIRA (https://issues.apache.org/jira/browse/STORM-1475) to track that and contribute our change back to the project.  We're cleaning a couple of things up right now, but I'm hopeful we will contribute it back soon.

Your second request could be a nice feature enhancement, can you open a JIRA for it? In my experience, these external bolts are a really nice way to get involved with the project as well. You could try adding a couple of features and contributing those.

Thanks!

From: Tech Id <te...@gmail.com>>
Reply-To: "user@storm.apache.org<ma...@storm.apache.org>" <us...@storm.apache.org>>
Date: Friday, March 18, 2016 at 9:45 PM
To: "user@storm.apache.org<ma...@storm.apache.org>" <us...@storm.apache.org>>
Subject: external/storm-elasticsearch - upgrade requested

Hi,

I see that the version of elastic-search used in external/storm-elasticsearch/pom.xml is quite old (1.6.0) while the latest elastic-search is 2.2.0

2.x version is not compatible with 1.x version of elastic-search and so I request you to upgrade.

Also, current storm-elasticsearch uses TransportClient of elastic-search but does not expose many of the useful options in the TransportClient (like routing).

Request you to expose them to the users too.


Thanks
Tid

Re: external/storm-elasticsearch - upgrade requested

Posted by Tech Id <te...@gmail.com>.
Thanks Aaron,

Did you have a chance to compare the elasticsearch-hadoop (
https://www.elastic.co/guide/en/elasticsearch/hadoop/current/storm.html)
with the storm-elasticsearch (
https://github.com/apache/storm/tree/master/external/storm-elasticsearch) ?

Former uses REST client while the latter uses TransportClient.

It would be interesting to know some performance numbers between them.

Thanks !

On Mon, Mar 21, 2016 at 5:40 AM, Aaron.Dossett <Aa...@target.com>
wrote:

> Hi,
>
> The best way to make feature requests like this is via the Apache Jira. (
> https://issues.apache.org/jira/browse/STORM/)
>
> As it happens, my team (at Target) has adapted the elastic search bolt for
> 2.X and we are using it in production.  We opened a JIRA (
> https://issues.apache.org/jira/browse/STORM-1475) to track that and
> contribute our change back to the project.  We’re cleaning a couple of
> things up right now, but I’m hopeful we will contribute it back soon.
>
> Your second request could be a nice feature enhancement, can you open a
> JIRA for it? In my experience, these external bolts are a really nice way
> to get involved with the project as well. You could try adding a couple of
> features and contributing those.
>
> Thanks!
>
> From: Tech Id <te...@gmail.com>
> Reply-To: "user@storm.apache.org" <us...@storm.apache.org>
> Date: Friday, March 18, 2016 at 9:45 PM
> To: "user@storm.apache.org" <us...@storm.apache.org>
> Subject: external/storm-elasticsearch - upgrade requested
>
> Hi,
>
> I see that the version of elastic-search used
> in external/storm-elasticsearch/pom.xml is quite old (1.6.0) while the
> latest elastic-search is 2.2.0
>
> 2.x version is not compatible with 1.x version of elastic-search and so I
> request you to upgrade.
>
> Also, current storm-elasticsearch uses TransportClient of elastic-search
> but does not expose many of the useful options in the TransportClient (like
> routing).
>
> Request you to expose them to the users too.
>
>
> Thanks
> Tid
>

Re: external/storm-elasticsearch - upgrade requested

Posted by "Aaron.Dossett" <Aa...@target.com>.
Hi,

The best way to make feature requests like this is via the Apache Jira. (https://issues.apache.org/jira/browse/STORM/)

As it happens, my team (at Target) has adapted the elastic search bolt for 2.X and we are using it in production.  We opened a JIRA (https://issues.apache.org/jira/browse/STORM-1475) to track that and contribute our change back to the project.  We're cleaning a couple of things up right now, but I'm hopeful we will contribute it back soon.

Your second request could be a nice feature enhancement, can you open a JIRA for it? In my experience, these external bolts are a really nice way to get involved with the project as well. You could try adding a couple of features and contributing those.

Thanks!

From: Tech Id <te...@gmail.com>>
Reply-To: "user@storm.apache.org<ma...@storm.apache.org>" <us...@storm.apache.org>>
Date: Friday, March 18, 2016 at 9:45 PM
To: "user@storm.apache.org<ma...@storm.apache.org>" <us...@storm.apache.org>>
Subject: external/storm-elasticsearch - upgrade requested

Hi,

I see that the version of elastic-search used in external/storm-elasticsearch/pom.xml is quite old (1.6.0) while the latest elastic-search is 2.2.0

2.x version is not compatible with 1.x version of elastic-search and so I request you to upgrade.

Also, current storm-elasticsearch uses TransportClient of elastic-search but does not expose many of the useful options in the TransportClient (like routing).

Request you to expose them to the users too.


Thanks
Tid