Re: Request for becoming a contributor

Done! And welcome! You are probably are already communicating, but I have CC'd Manu Zhang anyhow. On Mon, Jan 23, 2017 at 9:41 PM, Vincent Wang wrote: > Hi, > > This is Huafeng from Apache Gearpump(incubating) team and I'd like to make > contribution to Gearpump runner on

Request for becoming a contributor

Hi, This is Huafeng from Apache Gearpump(incubating) team and I'd like to make contribution to Gearpump runner on Beam. Would you mind adding me to the contributor list? My jira system email is huafeng.w...@intel.com Thanks, Huafeng

Re: Jenkins build became unstable: beam_PostCommit_Java_RunnableOnService_Dataflow #2089

The error looks to be the recent changes to PubsubIO, but probably not deep: https://builds.apache.org/job/beam_PostCommit_Java_RunnableOnService_Dataflow/org.apache.beam$beam-runners-google-cloud-dataflow-java/2089/testReport/junit/org.apache.beam.sdk.io/PubsubIOTest/testPrimitiveReadDisplayData/

Re: Jenkins build is back to stable : beam_PostCommit_Java_RunnableOnService_Dataflow #2088

Noting that this is _not_ back to stable, but that this build was triggered by me to test that the revert _would_ get it back to stable. On Mon, Jan 23, 2017 at 7:31 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See

Re: Committed vs. attempted metrics results

For the short term, it seems like staying with the existing Query API and allowing runner's to throw exceptions if a user issues a query that is not supported is reasonable. It shouldn't affect the ability to run a Beam pipeline on other runners, since the Query API is only exposed *after* the

Re: Jenkins build became unstable: beam_PostCommit_Java_RunnableOnService_Dataflow #2085

Pulling out the error: but: The following white-listed scopes did not have matching classes on the API surface: No Classes in package "com.fasterxml.jackson.annotation" No Classes in package "com.fasterxml.jackson.core" No Classes in package

Re: [VOTE] Merge Python SDK to the master branch

Hi all, The vote passed with the following result: +1: Davor Bonaci, Frances Perry, Kenneth Knowles, Jean-Baptiste Onofré, Dan Halperin, Robert Bradshaw, Sergio Fernández, Ismaël Mejía, Lukasz Cwik, Amit Sela There are no disapproving votes. Thank you all for voting. I will work on the merge,

Re: Subscription to to beam project

+original mailer, assuming he is not on dev@... On Sun, Jan 22, 2017 at 7:31 PM, Davor Bonaci wrote: > Welcome! Please check out the support page [1] with all mailing lists and > subscribe links. > > [1] https://beam.apache.org/get-started/support/ > > On Sat, Jan 21, 2017 at

Re: Release 0.5.0

Hi Davor, Yes, it makes sense to prepare 0.5.0. If no other wants to take this release, I'm volunteer. Regards JB On 01/23/2017 07:29 PM, Davor Bonaci wrote: It's been about a month since the last release, so we should start preparing the next one. We have plenty of great content to share

Release 0.5.0

It's been about a month since the last release, so we should start preparing the next one. We have plenty of great content to share with our users! We have a couple of release blocking bugs [1], but they seem to be heading towards a conclusion. Is anybody aware of any other release blocking

Re: Beam Fn API

Responded inline. On Sat, Jan 21, 2017 at 8:20 AM, Amit Sela wrote: > This is truly amazing Luke! > > If I understand this right, the runner executing the DoFn will delegate the > function code and input data (and state, coders, etc.) to the container > where it will

Re: [VOTE] Merge Python SDK to the master branch

+1 On Mon, Jan 23, 2017 at 1:23 AM, Ismaël Mejía wrote: > [X] +1, Merge python-sdk branch to master after the 0.5.0 release > > Big +1, unbounded support will come/stabilize later on (as it happened with > InProcessRunner), visibility is more important. > > On Mon, Jan 23,