Idea for new Bolt

[Idan Fridman <id...@gmail.com>]

Hi All,

recently I had to implement a http-async-request inside Storm topology's
bolt.

I had to deal with Threads, async response, etc..

I was relaying on external library:
https://github.com/AsyncHttpClient/async-http-client

 I thought about take my case and make it generic by contribute a new
bolt(AsyncHttpBolt).

The bolt will take tuple as input and convert it into request.
the async response also will be received and converted into an output tuple
and auto emitted.

This bolt will be configured by an input-mapper so the implementation (url,
query params, etc..) will be up to the user.

What do you think?

thanks,
Idan.

Re: Idea for new Bolt

[Bobby Evans <ev...@yahoo-inc.com.INVALID>]

I know we have had people doing the same sort of thing internally here, and have run into lots of problems around timeouts and other issues.  I think having a common bolt for doing this would be great, so others don't have to reinvent the wheel. - Bobby
 

     On Wednesday, December 24, 2014 3:22 AM, Idan Fridman <id...@gmail.com> wrote:
   

 Hi All,

recently I had to implement a http-async-request inside Storm topology's
bolt.

I had to deal with Threads, async response, etc..

I was relaying on external library:
https://github.com/AsyncHttpClient/async-http-client

 I thought about take my case and make it generic by contribute a new
bolt(AsyncHttpBolt).

The bolt will take tuple as input and convert it into request.
the async response also will be received and converted into an output tuple
and auto emitted.

This bolt will be configured by an input-mapper so the implementation (url,
query params, etc..) will be up to the user.

What do you think?

thanks,
Idan.