We at Hazelcast are looking into writing a Beam runner for Hazelcast Jet (
https://github.com/hazelcast/hazelcast-jet). I wanted to introduce myself
as we'll likely have questions as we start development.
Some of the things I'm wondering about currently:
* Currently there seems to be a guide avai
t; know, but is now the responsibility of the "SDK harness", aka
> language-specific coprocessor. For Python & Go & here> you really want to use the portability protos and the portable Flink
> runner is the best model.
>
> Kenn
>
>
> On Fri, Feb 15, 2019 at 2
> it would be possible to build something like this on top of the existing
> translation.
>
> Cheers,
> Max
>
> On 20.03.19 13:07, Can Gencer wrote:
> > Hi again,
> >
> > We've made some progress on the runner since writing this more than a
> > mo
I had a look at "GreedyPipelineFuser" and indeed this was what exactly I
was talking about.
Is https://beam.apache.org/roadmap/portability/ still the best information
about the portable runners or is there a more in-depth guide available
anywhere?
On Wed, Mar 20, 2019 at 2:29 PM
Hi,
I'd like to also mention that Hazelcast is part of GSoC this year and one
of the proposal ideas we have put forward is to implement the portable
runner for Hazelcast Jet (there is already an "old-style" runner). It's a
good opportunity to understand the internals of a stream processing engine
