Hi Kenn. It took me a while to migrate our code to the Beam repo, but I finally have been able to create the Pull Request you asked for, this is it: https://github.com/apache/beam/pull/8410
Looking forward to your feedback! Best regards, Jozsef On 2019/04/19 20:52:42, Kenneth Knowles <[email protected]> wrote: > The ValidatesRunner tests are the best source we have for knowing the > capabilities of a runner. Are there instructions for running the tests? > > Assuming we can check it out, then just open a PR to the website with the > current capabilities and caveats. Since it is a big deal and could use lots > of eyes, I would share the PR link on this thread. > > Kenn > > On Thu, Apr 18, 2019 at 11:53 AM Jozsef Bartok <[email protected]> wrote: > > > Hi. We at Hazelcast Jet have been working for a while now to implement a > > Java Beam Runner (non-portable) based on Hazelcast Jet ( > > https://jet.hazelcast.org/). The process is still ongoing ( > > https://github.com/hazelcast/hazelcast-jet-beam-runner), but we are > > aiming for a fully functional, reliable Runner which can proudly join the > > Capability Matrix. For that purpose I would like to ask what’s your process > > of validating runners? We are already running the @ValidatesRunner tests > > and the Nexmark test suite, but beyond that what other steps do we need to > > take to get our Runner to the level it needs to be at? > > >
