Thanks everyone for your enthusiasms!
I'll try to organize something very shortly.
On Thu, Feb 23, 2017 at 12:48 AM, Jean-Baptiste Onofré
wrote:
> Agree
>
> An agenda would be useful.
>
> Further more, I think it would be great to have minute notes on the
> mailing list:
Hi Kenn,
Thanks a lot for explaining. As the SimpleDoFnRunner only takes one
StepContext object in its arguments, do you mean the runner should create a
new SimpleDoFnRunner for each key?
Best,
Shen
On Thu, Feb 23, 2017 at 10:16 PM, Kenneth Knowles
wrote:
> Hi Shen,
Hi all,
Yesterday, there was an announcement from TensorFlow community about the
new tf.Transform library [1]. It is a library that allows users to define
pre-processing pipelines and run using large scale data processing
frameworks. It is a library specifically designed to work with Apache Beam.
Beam and TensorFlow coming together -- a big deal for us!
On Thu, Feb 23, 2017 at 3:49 PM, Ahmet Altay
wrote:
> Hi all,
>
> Yesterday, there was an announcement from TensorFlow community about the
> new tf.Transform library [1]. It is a library that allows users to
Hi,
I am trying to understand how a runner can support the Stateful ParDo.
Currently our runner relies on the SimpleDoFnRunner (Beam-0.5.0). But it
cannot pass ParDoTest#testValueStateSideOutput (
+1 to do it periodically about different subjects.
It is a good idea to have a sort of mini agenda, in the sense that the two
previous meetings had really different focus, the first one was about
contributors meeting each other and discussion of ongoing work just after
the project started on
Agree
An agenda would be useful.
Further more, I think it would be great to have minute notes on the
mailing list: remember, if it's not on the mailing list, it never
happened ;)
My $0.01 ;)
Regards
JB
On 02/23/2017 09:26 AM, Ismaël Mejía wrote:
+1 to do it periodically about different