Re: Suggestion for Writing Sink Implementation

Thanks a lot Eugene. >>>My immediate requirement is to run this Sink on FlinkRunner. Which mandates that my implementation must also implement SinkFunction<>. In that >>>case, none of the Sink<> methods get called anyway. I am using FlinkRunner. The Sink implementation that i was writing by

Re: Suggestion for Writing Sink Implementation

Hi Sumit, All reusable parts of a pipeline, including connectors to storage systems, should be packaged as PTransform's. Sink is an advanced API that you can use under the hood to implement the transform, if this particular connector benefits from this API - but you don't have to, and many

Fwd: Suggestion for Writing Sink Implementation

Hi Please suggest me on what is the best way to write a Sink in Beam. I see that there is a Sink abstract class which is in experimental state. What is the expected outcome of this one? Do we have the api frozen, or this could still change? Most of the existing Sink implementations like

Re: Podling Report Reminder - August 2016

Hi James, Sure, please go ahead. I propose to send the draft on the mailing list for review. When reviewed, we will add on the incubator wiki (I will help you if you don't have the permission to do so). Regards JB On 07/27/2016 07:22 PM, James Malone wrote: Hi all, Unless anyone

Re: Podling Report Reminder - August 2016

+1 On Wed, Jul 27, 2016, 22:12 Dan Halperin wrote: > +1 on all the above. > > On Wed, Jul 27, 2016 at 12:07 PM, Jean-Baptiste Onofré > wrote: > > > Hi James, > > > > Sure, please go ahead. > > > > I propose to send the draft on the mailing list

Re: Podling Report Reminder - August 2016

+1 on all the above. On Wed, Jul 27, 2016 at 12:07 PM, Jean-Baptiste Onofré wrote: > Hi James, > > Sure, please go ahead. > > I propose to send the draft on the mailing list for review. When reviewed, > we will add on the incubator wiki (I will help you if you don't have the

Re: Podling Report Reminder - August 2016

Hi all, Unless anyone disagrees, I will volunteer to write this podling report. My goal is to get a draft out this week so we can review it as a project before we submit it to the Incubator PMC. Cheers! James On Wed, Jul 27, 2016 at 4:47 AM wrote: > Dear podling, > >

Re: Build failed in Jenkins: beam_Release_NightlySnapshot #115

Hi Ken, I gonna take a look tonight. Regards JB On 07/27/2016 05:45 PM, Kenneth Knowles wrote: This is day 2 of proxy errors when deploying the nightly snapshot, right? Apologies if I missed a thread about the prior failure. Is anyone already looking at this? On Wed, Jul 27, 2016 at 12:03

Build failed in Jenkins: beam_Release_NightlySnapshot #115

See Changes: [mxm] [flink] improve example section in README [owenzhang1990] [BEAM-489] remove headerLocation from maven-checkstyle-plugin [dhalperi] Remove spark test dependency on DirectRunner [dhalperi] Spark tests:

Podling Report Reminder - August 2016

Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 17 August 2016, 10:30 am PDT. The report for your podling will form

Re: how to work on gearpump-runner branch

Hi Manu, Any time you want to merge master into your branch just send a PR -- any of us will be happy to review and merge but especially Kenn and I. (Python-sdk has been doing the same.) Dan On Tue, Jul 26, 2016 at 10:13 PM, Manu Zhang wrote: > Hi JB, > > Thanks. If