Re: Contribute

An extra tip: ./gradlew tasks --all should show you a bunch of existing tasks that you can run, and ./gradlew projects --all does the same for projects. -P. On Fri, Aug 10, 2018, 10:33 PM Trần Thành Đạt wrote: > Thank you, Rui, > > I have the same question. > I will start running ./gradlew :task

Re: Contribute

Thank you, Rui, I have the same question. I will start running ./gradlew :task to explore Beam codebase On Sat, Aug 11, 2018 at 11:45 AM, Rui Wang wrote: > Hi Shayak! > > Thanks for your interest. > > Beam uses Gradle to build and test code. One thing I found was very useful > when I started t

Re: Contribute

Hi Shayak! Thanks for your interest. Beam uses Gradle to build and test code. One thing I found was very useful when I started to contribute was a tip about Gradle: you can run ./gradlew :task to get a list of commands that you can run with Gradle under a module, which includes compile/run/build

Re: Contribute

Hello JB, I did take a look into the contribute page. These are the list of things I can help out with: 1. Python 3 support 3. MapReduce Runner 4. Apache Spark 2.0 Runner To get started, can you forward me some documentation that would give me a brief code walkthrough. Also, I will try to pull th

Re: [Discussion] Clarify the support story for released Beam versions

Thanks, I can see the reasoning for LTS releases based upon some enterprise customers needs. Forgot about the 2.1.1 Python release. Thanks for pointing that out. On Fri, Aug 10, 2018 at 4:47 PM Ahmet Altay wrote: > > On Fri, Aug 10, 2018 at 12:33 PM, Lukasz Cwik wrote: > >> I like the ideas th

Re: [Discussion] Clarify the support story for released Beam versions

On Fri, Aug 10, 2018 at 12:33 PM, Lukasz Cwik wrote: > I like the ideas that your proposing but am wondering what value if any do > supporting LTS releases add? We maintain semantic versioning and I would > expect that most users would be using the latest released version if not > the release jus

Re: [HELP] Blog post for 2.6.0 Release

Hello everyone, here's a PR for the blog post: https://github.com/apache/beam-site/pull/533 Last call for opinions : ) Best -P. On Fri, Aug 10, 2018 at 9:47 AM Pablo Estrada wrote: > Hello everyone, > a bump here on asking for your contributions to the 2.6.0 release blog > post. > Best > -P. >

Test failures list

Hi everyone, I'm following up on tackling post-commit tests greenness. (See beam post-commit policies ) During this week, I've assembled a list of most problematic flaky or failing tests

Re: Apache Beam Newsletter - August 2018

Thank you for compiling this Rose! Interesting stories and news. -P. On Fri, Aug 10, 2018 at 12:37 PM Rose Nguyen wrote: > [image: Beam.png] > > August 2018 | Newsletter > > What’s been done > > [image: Tick - done] > > Apache Beam 2.6.0 Release > >- > >The Apache Beam team is pleased to

Re: PreCommits not being filtered by PR contents

I filed https://issues.apache.org/jira/browse/BEAM-5126 for the issue. On Fri, Aug 10, 2018 at 11:37 AM Jean-Baptiste Onofré wrote: > I saw the issue, but I didn't have time to investigate. > > Regards > JB > > On 10/08/2018 20:31, Lukasz Cwik wrote: > > We used to run PreCommits based upon the

Apache Beam Newsletter - August 2018

[image: Beam.png] August 2018 | Newsletter What’s been done [image: Tick - done] Apache Beam 2.6.0 Release - The Apache Beam team is pleased to announce the release of 2.6.0 version! This is the second release under the new build system, and the process has kept improving. -

Re: [Discussion] Clarify the support story for released Beam versions

I like the ideas that your proposing but am wondering what value if any do supporting LTS releases add? We maintain semantic versioning and I would expect that most users would be using the latest released version if not the release just before that. There is likely a long tail of users who will us

Re: [Discussion] Clarify the support story for released Beam versions

I think this all sounds reasonable, and I think it would be a good story for our users. We don't have much experience with patching releases, but I guess it's a matter of learning and improving over time. -P. On Wed, Aug 8, 2018 at 9:04 PM Ahmet Altay wrote: > Hi all, > > I would like us to clar

Re: PreCommits not being filtered by PR contents

I saw the issue, but I didn't have time to investigate. Regards JB On 10/08/2018 20:31, Lukasz Cwik wrote: > We used to run PreCommits based upon the contents of the PR but it seems > as though this has regressed while I was on vacation. > > Is anyone working on resolving this and does anyone ha

Re: [Vote] Create apache-beam-wheels repo like beam-site

+1 Regards JB On 09/08/2018 22:10, Boyuan Zhang wrote: > Hey all, > > With some ongoing discussions happened in "Apache Beam Python Wheels > Repository" thread, we are decided to move forward to start this vote > process. We want to create a new apache repo like beam-site >

PreCommits not being filtered by PR contents

We used to run PreCommits based upon the contents of the PR but it seems as though this has regressed while I was on vacation. Is anyone working on resolving this and does anyone have any further details as I couldn't find any details in JIRA?

Re: [Vote] Create apache-beam-wheels repo like beam-site

+1 : ) On Thu, Aug 9, 2018 at 1:39 PM Ahmet Altay wrote: > +1 > > On Thu, Aug 9, 2018 at 1:10 PM, Boyuan Zhang wrote: > >> Hey all, >> >> With some ongoing discussions happened in "Apache Beam Python Wheels >> Repository" thread, we are decided to move forward to start this vote >> process. We

Re: [HELP] Blog post for 2.6.0 Release

Hello everyone, a bump here on asking for your contributions to the 2.6.0 release blog post. Best -P. On Wed, Aug 8, 2018 at 4:20 PM Pablo Estrada wrote: > Hello all, > During my work on the release, I missed that we have started doing blog > posts for every release. I decided to announce the re

Re: [DISCUSS] Communicating in dev@

+1 to all points made so far. I think docs are great for collaborating on bigger proposals, but mailing list summaries are very helpful since it's often unpractical to click through on each and every one (plus I can search archives more effectively that way). And email for shorter proposals is also

Re: Looking for java elasticsearch client reviewer

I can do the review as well, as I did the original ES IO with Etienne. Regards JB On 10/08/2018 17:25, Alexey Romanenko wrote: > Hi Tormod, > > Thank you for your contribution! > > As I see in this PR, there are two suggestions for reviewers - Etienne > Chauchot (echauchot) and Ismaël Mejía (ie

Re: Looking for java elasticsearch client reviewer

Hi Tormod, Thank you for your contribution! As I see in this PR, there are two suggestions for reviewers - Etienne Chauchot (echauchot) and Ismaël Mejía (iemejia). So, you can send a request for review to them directly from your PR. AFAIK, they are on holidays for the moment but they will back

Looking for java elasticsearch client reviewer

I had to fork the elasticsearch client for a project I am working on and created a pull request #6200 "Java elasticsearch client support for reading documents with metadata." Who should I mention as reviewer? I just added a new Reader option "withMetadata" in order to access the whole elastic resu

Re: Contribute

Hi, you can take a look on the Contribution Guide: https://beam.apache.org/contribute/ Regards JB On 10/08/2018 09:18, Shayak Sadhu wrote: > Hi Team, > > I would like to contribute to Apache Beam. > > Regards, > Shayak -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Tal

Contribute

Hi Team, I would like to contribute to Apache Beam. Regards, Shayak