Re: [ANNOUNCE] A brand new DoFn @ HEAD (action required)
Thanks Kenn! I am impressed that this was doable so quickly -- only a week after the Beam dev community +1ed the heck out of it. This is going to be great. (More info on the original dev thread: http://mail-archives.apache.org/mod_mbox/incubator-beam-dev/201607.mbox/%3CCAN_Ypr3P1xmVL9O7kvy6LSMeNz7k3Dpk9QaSt8UmV686ZzuKaQ%40mail.gmail.com%3E ) On Wed, Aug 3, 2016 at 6:44 PM, Kenneth Knowleswrote: > Hi all, > > We have just incorporated a major feature into the master branch of the > Beam codebase: a new DoFn. Assuming you are tracking HEAD, this will > require some (easy) adjustment to your pipelines. > > The experimental feature that was in the codebase as DoFnWithContext is > now just "DoFn" for Beam. It is a radical enabler of new features, most > excitingly our design for stateful DoFn and timer-based callbacks. But does > require you to do some search-and-replace in your pipelines. > > For a DoFn like this: > > new DoFn () { > @Override > public void processElement(ProcessContext c) { … } > } > > now you'll need to write this: > > new DoFn () { > @ProcessElement // <-- This is the only difference > public void processElement(ProcessContext c) { … } > } > > Likewise for your startBundle() and finishBundle() methods, you'll replace > @Override with @StartBundle and @FinishBundle, respectively. If you want to > see more, we have ported a number of examples and tests to use this new > DoFn and will be proceeding with the rest and the documentation. > > If you don't want to make any change right now, you may want to delay > tracking HEAD. I have tagged the last commit prior to the change so you can > `git checkout OldDoFn` and move beyond that point when you are ready. > > Kenn >
Re: [INFO] Apache Beam wikipedia page
Hi Ismaël, good idea. Now we have provide content ;) Regards JB On 08/04/2016 12:08 AM, Ismaël Mejía wrote: Hello, I just realized that we didn’t have a wikipedia page for the project so I created a first version. https://en.wikipedia.org/wiki/Apache_Beam Ismaël ps. Since wikipedia fights abuse in an almost ‘maniac’ way, the article was marked as candidate for deletion so please feel free to help me improve it and discuss in the talk section the reasons to contest the deletion. -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
[ANNOUNCE] A brand new DoFn @ HEAD (action required)
Hi all, We have just incorporated a major feature into the master branch of the Beam codebase: a new DoFn. Assuming you are tracking HEAD, this will require some (easy) adjustment to your pipelines. The experimental feature that was in the codebase as DoFnWithContext is now just "DoFn" for Beam. It is a radical enabler of new features, most excitingly our design for stateful DoFn and timer-based callbacks. But does require you to do some search-and-replace in your pipelines. For a DoFn like this: new DoFn() { @Override public void processElement(ProcessContext c) { … } } now you'll need to write this: new DoFn () { @ProcessElement // <-- This is the only difference public void processElement(ProcessContext c) { … } } Likewise for your startBundle() and finishBundle() methods, you'll replace @Override with @StartBundle and @FinishBundle, respectively. If you want to see more, we have ported a number of examples and tests to use this new DoFn and will be proceeding with the rest and the documentation. If you don't want to make any change right now, you may want to delay tracking HEAD. I have tagged the last commit prior to the change so you can `git checkout OldDoFn` and move beyond that point when you are ready. Kenn