Hi guys, it got mentionned but without any concrete dates: when beam 3 work will be started?
I'm very interested in: 1. reworking the whole DAG API to ensure it is instrumentable (today the dag uses a tons of static utilities and internals which makes it not industrializable at all as soon as you are just on top of beam) 2. reworking the API definition in its own module not coupled to any implementation details (api/provider design) and 100% based on the sdf 3. rework the overall serialization (coders + transform serialization which is hardcoded today and not portable or industrializable at all) 4. make runners decorable properly and not just forked each time you need to modify some behavior for a particular case (+ indeed all the issues we hit and saw on the list) Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance>
