Jenkins build became unstable: beam_Release_NightlySnapshot #352

See

Re: BEAM-831 ParDo chaining for Apex runner

Hi All, I did the implementation as you mentioned and created a PR ( https://github.com/apache/beam/pull/2216) for CI and also for code related discussion. I'm writing unit tests for the code changes. If you get time, please have a look at the code and provide the feedback. Thanks in advance, Ch

Re: [PROPOSAL] Add 2.0.0 version in Jira

Fair enough, let's wait and as said, use the "First stable release" in Jira. Regards JB On 03/09/2017 11:04 PM, Davor Bonaci wrote: I added "First stable release" in JIRA as a version identifier a while back, to avoid any prejudice what that version might be called. I think it makes sense to re

Re: [Dev] GSoc 2017 "Beam Example(s) exploring public document datasets"

Thanks for the quick reply Kenneth. Currently I am going through *Apache Beam* installation and referring Programming Guide and Documentation. Please update me if their any suggestions. On 10 March 2017 at 09:14, Kenneth Knowles wrote: > Hi Milinda, > > Glad you are interested! I think it should

Re: [VOTE] Release 0.6.0, release candidate #1

bq. ran into a known issue [14] Currently BEAM-1674 is marked blocker. Would it be pushed to next release ? Cheers On Thu, Mar 9, 2017 at 4:07 PM, Ahmet Altay wrote: > Hi everyone, > > Please review and vote on the release candidate #1 for the version 0.6.0, > as follows: > [ ] +1, Approve the

Re: [Dev] GSoc 2017 "Beam Example(s) exploring public document datasets"

Hi Milinda, Glad you are interested! I think it should be very fun and rewarding. The student application period for Google Summer of Code opens on March 20th, so be sure to apply then. I also recommend subscribing to https://issues.apache.org/jira/browse/BEAM-1439. I will add some details there

Re: [VOTE] Release 0.6.0, release candidate #1

+1 Checked signature Ran test suite - all passed. On Thu, Mar 9, 2017 at 4:07 PM, Ahmet Altay wrote: > Hi everyone, > > Please review and vote on the release candidate #1 for the version 0.6.0, > as follows: > [ ] +1, Approve the release > [ ] -1, Do not approve the release (please provide spe

[Dev] GSoc 2017 "Beam Example(s) exploring public document datasets"

Hi, I'm Milinda Kasun, I am a Final year undergraduate from the Department of Computer Science and Engineering (University of Moratuwa, Sri Lanka). I have experience on development with Java and Python. I would like do this project for GSoC 2017. It would be greatly appreciated if you could help me

[VOTE] Release 0.6.0, release candidate #1

Hi everyone, Please review and vote on the release candidate #1 for the version 0.6.0, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) The complete staging area is available for your review, which includes: * JIRA release notes [1], *

Re: Fwd: Jenkins build is still unstable: beam_PostCommit_Java_RunnableOnService_Flink #1866

I commented there, but in the meantime I suggest suppressing the UsesTimersInParDo test category. You lose some coverage on tests that were passing, but they are tests of a feature that is probably not really safe to use. On Thu, Mar 9, 2017 at 7:17 AM, Aljoscha Krettek wrote: > Figured out what

Re: [PROPOSAL] Add 2.0.0 version in Jira

I added "First stable release" in JIRA as a version identifier a while back, to avoid any prejudice what that version might be called. I think it makes sense to resolve (newly fixed) issues against that version. Once we finalize the name of that release, we can easily rename it to either "1.0.0" or

Re: Add GitHub topics to Beam repository

We certainly cannot do this ourselves, but it is within the realm of possibility that Apache Infra can assign tags to our GitHub repositories. Looking at the tags that already exist, perhaps we could go with: * apache-beam * big-data * data-processing * data-analysis * data-science * data-analytic

Re: [PROPOSAL] Add 2.0.0 version in Jira

Well, for now at least. We have to use something for fixed issues.. On Thu, Mar 9, 2017 at 6:32 PM Jean-Baptiste Onofré wrote: > By the way, waiting the end of this discussion, we can use "First stable > release" as version in Jira. > > Regards > JB > > On 03/09/2017 07:21 AM, Jean-Baptiste Onof

Re: [PROPOSAL] Add 2.0.0 version in Jira

By the way, waiting the end of this discussion, we can use "First stable release" as version in Jira. Regards JB On 03/09/2017 07:21 AM, Jean-Baptiste Onofré wrote: Hi all, Release branch for 0.6.0 has been created but the next cycle version has not been created in Jira. I propose to create

Re: Fwd: Jenkins build is still unstable: beam_PostCommit_Java_RunnableOnService_Flink #1866

Figured out what it is: https://issues.apache.org/jira/browse/BEAM-1674 Unfortunately, I don't have a solution right now. On Thu, Mar 9, 2017, at 11:36, Aljoscha Krettek wrote: > I'm looking into the recent streak of unstable builds. > > - Original message - > From: Apache Jenkins Server

Re: Add GitHub topics to Beam repository

Hi Aviem, thanks for the hit ! I thought about reviewers feature too but it requires "write" access to github, which is not possible as github is just a mirror of Apache git. Regards JB On 03/09/2017 01:31 PM, Aviem Zur wrote: About a month ago GitHub introduced topics, which let GitHub use

Add GitHub topics to Beam repository

About a month ago GitHub introduced topics, which let GitHub users query for repositories by topics (domains that the repos deal with). We can leverage these to increase Beam's exposure on GitHub. Example topics we could add: big-data, google-cloud-dataflow, spark, flink, apex, gearpump We can als

Fwd: Jenkins build is still unstable: beam_PostCommit_Java_RunnableOnService_Flink #1866

I'm looking into the recent streak of unstable builds. - Original message - From: Apache Jenkins Server To: comm...@beam.apache.org, k...@google.com, al...@google.com Subject: Jenkins build is still unstable: beam_PostCommit_Java_RunnableOnService_Flink #1866 Date: Thu, 9 Mar 2017 01:45:1

Re: [BEAM-135] Utilities for "batching" elements in a DoFn

Hi all, We had a discussion with Kenn yesterday about point 1 bellow, I would like to note it here on the ML: Using new method timer.set() instead of timer.setForNowPlus() makes the timer fire at the right time. Another thing, regarding point 2: if I inject the window in the @Ontimer metho