Erik is correct, that is the right branch. It was initially unmodified, but I
just merged the initial pull request so others are open to create pull requests
against that branch now.
-Taylor
> On Nov 23, 2016, at 1:07 PM, Erik Weathers
> wrote:
>
> Hugo,
>
> This appears to be the branch:
>
Hugo,
This appears to be the branch:
- https://github.com/apache/storm/tree/beam-runner
- Erik
On Wed, Nov 23, 2016 at 9:34 AM, Hugo Da Cruz Louro
wrote:
> I somehow missed this email … I would like to contribute to this effort as
> well. Please keep me posted.
> Thanks.
>
> > On Oct 19, 2
I somehow missed this email … I would like to contribute to this effort as
well. Please keep me posted.
Thanks.
> On Oct 19, 2016, at 8:51 AM, Satish Duggana wrote:
>
> +1, waiting for that. :)
> Currently,there are API changes going on in Beam. It seem they plan to get
> that done by the end o
+1, waiting for that. :)
Currently,there are API changes going on in Beam. It seem they plan to get
that done by the end of 2016.
~Satish.
On Wed, Oct 19, 2016 at 9:19 PM, Bobby Evans
wrote:
> +1 - Bobby
>
> On Wednesday, October 19, 2016 10:30 AM, Arun Mahadevan <
> ar...@apache.org> wrote
+1 - Bobby
On Wednesday, October 19, 2016 10:30 AM, Arun Mahadevan
wrote:
+1
On 10/19/16, 8:58 PM, "P. Taylor Goetz" wrote:
>If there are no objections, I’d like to create the feature branch and push
>what I have so far. I’ve not had too much time lately to work on it, but
>other’s
+1
On 10/19/16, 8:58 PM, "P. Taylor Goetz" wrote:
>If there are no objections, I’d like to create the feature branch and push
>what I have so far. I’ve not had too much time lately to work on it, but
>other’s have expressed interest in contributing so I’d like to make it
>available.
>
>-Taylo
If there are no objections, I’d like to create the feature branch and push what
I have so far. I’ve not had too much time lately to work on it, but other’s
have expressed interest in contributing so I’d like to make it available.
-Taylor
> On Sep 19, 2016, at 11:15 AM, Bobby Evans wrote:
>
>
+1 on the idea. I would love to contribute, but I doubt I will find time to do
it any time soon. - Bobby
On Friday, September 16, 2016 12:05 AM, Satish Duggana
wrote:
Taylor,
I am interested in contributing to this effort. Gone through Beam APIs
earlier and had some initial thoughts o
Taylor,
I am interested in contributing to this effort. Gone through Beam APIs
earlier and had some initial thoughts on Storm runner. We can start with
existing core storm constructs but it is better to design in such a way
that these can be replaced with new APIs.
Thanks,
Satish.
On Fri, Sep 16,
I'm open to change, but yes, I started with core storm since it offers the most
flexibility wrt how Beam constructs are translated.
-Taylor
> On Sep 15, 2016, at 5:51 PM, Roshan Naik wrote:
>
> Good idea. Will the Beam API be implemented to run on top Storm Core
> primitives ?
> -roshan
>
>
Good idea. Will the Beam API be implemented to run on top Storm Core
primitives ?
-roshan
On 9/15/16, 2:00 PM, "P. Taylor Goetz" wrote:
>I¹ve been tinkering with implementing an Apache Beam runner on top of
>Storm and would like to open it up so others in the community can
>contribute. To that
I’ve been tinkering with implementing an Apache Beam runner on top of Storm and
would like to open it up so others in the community can contribute. To that end
I’d like to propose creating a feature branch for that work if there are others
who are interested in getting involved. We did that a wh
12 matches
Mail list logo
