Re: Beam Interview

Last call. If you want your words of wisdom forever kept in the annals of Apache Beam lore, I'm publishing tomorrow (7-13) at 9 AM PT. On Mon, Jul 11, 2016 at 11:13 PM Tyler Akidau wrote: > +1. Thanks a lot for putting this together. :-) > > On Mon, Jul 11, 2016 at 9:33 PM

Re: New apache_beam branch ?

Hi JB, Actually, this is a good time for a process question. How do we clean this up -- do we have to file an INFRA ticket? Presumably we can't/shouldn't be able to just push a deletion of the branch. Thanks, Dan On Tue, Jul 12, 2016 at 9:39 AM, Jean-Baptiste Onofré wrote:

Re: New apache_beam branch ?

Hi Silviu, thanks to the update ! And no worries ;) Regards JB On 07/12/2016 05:30 PM, Silviu Calinoiu wrote: This change was supposed to go into python-sdk branch. We will clean up today. I just noticed that the python-sdk branch did not have the change and was scratching my head where did

Re: New apache_beam branch ?

This change was supposed to go into python-sdk branch. We will clean up today. I just noticed that the python-sdk branch did not have the change and was scratching my head where did it go :-) Thanks for noticing Jean-Baptiste! On Tue, Jul 12, 2016 at 7:51 AM, Jean-Baptiste Onofré

Re: [jira] [Commented] (BEAM-434) When examples write output to file it creates many output files instead of one

If we go with any option that restricts the number of outputs then in the example we should discuss what it does and why it is not considered a good thing. On Tue, Jul 12, 2016 at 2:11 AM, Amit Sela (JIRA) wrote: > > [ >