Re: Failure in Apex runner

On that same subject: in the SDK-angnostic proto for a pipeline there is no such thing as a main output [1]. The distinction between single and multiple output ParDo is SDK-specific. Kenn [1] https://github.com/apache/beam/blob/master/sdks/common/runner-api/src/main/proto/beam_runner_api.proto#L1

Re: BEAM-933 - Not reproduceable

I think the key line you will want to change is here: https://github.com/apache/beam/blob/master/examples/java/pom.xml#L375 On Sun, Jul 9, 2017 at 12:17 AM, Apache Enthu wrote: > Hi, > > Is BEAM-933 already fixed? I'm unable to reproduce the bug by running maven > build. Here's what i see: > > [

Re: BEAM-934 - Jira permission and pull request

Just a tiny correction - I think the JIRA role "contributor" for the Beam can take JIRAs without a committer assigning to them. But definitely you _must_ have this role or even a committer cannot give you a JIRA. What is your JIRA account, so I can add you as a contributor? Kenn On Sun, Jul 9, 2

Re: BEAM-934 - Jira permission and pull request

By Jira ID, I mean YOUR account ID. Committer is a long process: https://beam.apache.org/contribute/contribution-guide/#granting-more-rights-to-a-contributor I suggest to take a long on how Apache works: http://www.apache.org/ Regards JB On 07/09/2017 07:47 PM, Apache Enthu wrote: Thanks J

Re: BEAM-934 - Jira permission and pull request

Thanks JB. Jira Id is in Subject BEAM-934. https://issues.apache.org/jira/browse/BEAM-934 How do i get added as committer please? Or are there any criteria for me to be added to as Committer? Thanks, Almas On Sun, Jul 9, 2017 at 5:40 PM, Jean-Baptiste Onofré wrote: > Hi, > > you have to be com

Re: [PROPOSAL] Connectors for memcache and Couchbase

For the source: Do you plan to support enumerating all the keys via cachedump / lru_crawler metadump / ...? If there is an option which doesn't require enumerating the keys, how will splitting be done (no splitting / splitting on slab ids / ...)? Can the cache be read while its still being modified

Re: Failure in Apex runner

Yes. Semantically all outputs from a ParDo are equivalent, so the watermark should traverse them all. The only reason a "default" output exists is for convenience so we don't force users to always specify an output tag. On Sun, Jul 9, 2017 at 12:03 AM, Thomas Weise wrote: > This error turns out

Re: BEAM-934 - Jira permission and pull request

Hi, you have to be committer to do the assignment. If you provide your Jira ID, I will assign the Jira to you. Regards JB On 07/09/2017 08:30 AM, Apache Enthu wrote: Hi, I'm newbie in this project and i have picked up simple jira from the open jira list. It seems i don't have permission to

Build failed in Jenkins: beam_Release_NightlySnapshot #472

See -- [...truncated 1.18 MB...] 2017-07-09T07:31:48.256 [INFO] Downloading: https://repo.maven.apache.org/maven2/org/caffinitas/ohc/ohc-core/0.4.3/ohc-core-0.4.3.jar 2017-07

BEAM-933 - Not reproduceable

Hi, Is BEAM-933 already fixed? I'm unable to reproduce the bug by running maven build. Here's what i see: [INFO] --- maven-compiler-plugin:3.6.1:testCompile (default-testCompile) @ beam-examples-java --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 15 source files to C:\work

Re: Failure in Apex runner

This error turns out to be deterministic and debug friendly :) I enabled trace and found that the watermark "disappears" between the following two operators: [8/WriteCounts/WriteFiles/WriteBundles:ApexParDoOperator] [10/WriteCounts/WriteFiles/GroupUnwritten:ApexGroupByKeyOperator] GroupUnwritten