Re: [PROPOSAL] Preparing 2.5.0 release next week

Hi JB and all, I wanted to follow up on my previous email. The python streaming issue I mentioned is resolved and removed from the blocker list. Blocker list is empty now. You can go ahead with the release branch cut when you are ready. Thank you, Ahmet On Sun, May 13, 2018 at 8:43 AM,

Re: [PROPOSAL] Preparing 2.5.0 release next week

Hi JB, We found an issue related to using side inputs in streaming mode using python SDK. Charles is currently trying to find the root cause. Would you be able to give him some additional time to investigate the issue? Charles, do you have a JIRA issue on the blocker list? Thank you everyone

Re: [PROPOSAL] Python 3 support

e me permission to assign issues to myself? > And edit rights to the Kanban board? > > Robbe > > On Tue, 17 Apr 2018 at 22:56 Ahmet Altay <al...@google.com> wrote: > >> Kanban board for python 3: https://issues.apache.org/ >> jira/secure/RapidBoard.jspa?rapidView=245 >&

Re: Merge options in Github UI are confusing

I agree with Robert. In this case one size does not fit all. There are times, another round trip with a contributor would be frustrating to the author. Especially for new contributors. Having the option to squash and merge is useful in those cases. (For reference in the past we even helped new

Re: [PROPOSAL] Python 3 support

Kanban board for python 3: https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=245 (Thank you Davor!) Ahmet On Fri, Apr 6, 2018 at 6:32 PM, Reuven Lax <re...@google.com> wrote: > I had a similar problem. > > On Fri, Apr 6, 2018, 6:23 PM Ahmet Altay <al...@google.

Re: Gradle Status [April 11]

> Found another blocker in current artifacts creations: there is not pom.xml and pom.properties in META-INF. This is used by tools + libraries + integrations so it is quite important to not break it Romain, is there a JIRA for this issues? If not could you create one please? On Thu, Apr 12, 2018

Re: [PROPOSAL] Python 3 support

time >>>>> discovering what's been done). Tracking individual JIRAs and PRs gets >>>>> unwieldy, perhaps a spreadsheet with modules/packages on one axis and the >>>>> various automated/manual conversions along the other would be helpful? &g

Re: Python SDK feature set

On Mon, Apr 2, 2018 at 6:17 PM, Thomas Weise wrote: > Hi, > > I’m trying to find a summary of the feature set that is currently > supported in the Python SDK. I understand it is experimental and > currently only supports a subset of the Beam model like fixed interval > windows

Re: [ANNOUCEMENT] New Foundation members!

Congratulations to all of you! On Fri, Mar 30, 2018, 4:29 PM Pablo Estrada wrote: > Congratulations y'all! Very cool. > Best > -P. > > On Fri, Mar 30, 2018 at 4:09 PM Davor Bonaci wrote: > >> Now that this is public... please join me in welcoming three

Re: [PROPOSAL] Python 3 support

ld be great if we can enforce these per updated subpackage. >> Any insights on how to best accomplish this? >> > So you can look at some of the recent changes to tox.ini in the git log to > see what we’ve done so far around this I suspect you can repeat that same > pattern. >

Re: Dataflow throwing backend error

Hi Rajesh, This looks like a transient error from GCS. Beam SDK will retry tasks in the face of such errors and those typically do not make your pipeline fail. If you have additional questions please reach out to Dataflow support ( https://cloud.google.com/dataflow/support). Thank you, Ahmet On

Re: executing the pipeline from datalab

+ user, dev to bcc Eila, Is it possible that you are using an old version? I remember pending was missing in the dictionary and was added later. If that is not the reason, could you file a JIRA issue? Thank you, Ahmet On Fri, Mar 23, 2018 at 6:15 AM, Jean-Baptiste Onofré

Re: [PROPOSAL] Python 3 support

Thank you Robbe. I reviewed the document it looks reasonable to me. I will touch on some points that were not mentioned: - Runner exercise different code paths. Doing auto conversions and focusing on DirectRunner is not enough. It is worthwhile to run things on DataflowRunner as well. This can be

Re: Python PostCommit Broken

https://issues.apache.org/jira/browse/BEAM-3922 is the JIRA for tracking this. On Fri, Mar 23, 2018 at 10:51 AM, Pablo Estrada wrote: > Hello everyone, > I see that the Python PostCommit has been broken for a couple days. Is > there a PR / JIRA to track this? > See breakage:

Re: [PROPOSAL] Scripting extension based on Java JSR-223

Thank you Ismaël, this looks really cool. On Fri, Mar 23, 2018 at 5:33 AM, Jean-Baptiste Onofré wrote: > Hi, > > it sounds like a very good extension mechanism to PTransform. > > +1 > > Regards > JB > > On 03/23/2018 12:03 PM, Ismaël Mejía wrote: > > This is a really simple

Re: Apache beam DataFlow runner throwing setup error

Hi Rajesh, Have you looked at the worker-startup logs [1]? You should be able to see the setup error there. It is possible that something in your requirements file is failing to install in the workers. If that is the case, see Managing Python Pipeline Dependencies [2] for alternative options. You

Re: Pubsub API feedback

Thank you Udi. Left some high level comments on the PR. On Mon, Mar 19, 2018 at 5:13 PM, Udi Meiri wrote: > Hi, > I wanted to get feedback about the upcoming Python Pubsub API. It is > currently experimental and only supports reading and writing UTF-8 strings. > My current

Re: [VOTE] Release 2.4.0, release candidate #3

I was able to run hourly_team_score. I was passing a wrong argument. No need for an alarm. :) On Mon, Mar 19, 2018 at 5:33 PM, Ahmet Altay <al...@google.com> wrote: > +1 Thank you Robert. > > Verified python mobile gaming examples using the wheel files on direct > runner. Got

Re: [VOTE] Release 2.4.0, release candidate #3

+1 Thank you Robert. Verified python mobile gaming examples using the wheel files on direct runner. Got user_score working but hourly_team_score failed with ( https://issues.apache.org/jira/browse/BEAM-3824). Since this is an example, I think it is fine to continue with the release. I will work

Re: Contributing

Hi Austin, It was great meeting with you. We mentioned a list of starter bugs, here is that list [1]. It might give you some ides on where to start. [1]

Re: Proposal: build Python wheel distributions for Apache Beam releases

question of where these release > artifacts should be staged. (Eventually, of course, they'll be published to > PyPi). Should they be placed alongside the source artifacts in the svn > repository? > > > On Wed, Mar 7, 2018 at 3:00 PM Ahmet Altay <al...@google.com>

Re: Proposal: build Python wheel distributions for Apache Beam releases

ponding to the pyx files) that are > only built if Cython is present. We can (1) make sure Cython is > installed before installing apache beam into the container, and (2) > assert as part of the build process that these modules exist. > > > On Mon, Feb 12, 2018 at 9:32 PM, Ahmet Altay <a

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

-1 for the same reason as Ismaël. Python version is not updated in the release branch [1]. [1] https://github.com/apache/beam/blob/release-2.4.0/sdks/python/apache_beam/version.py#L21 On Wed, Mar 7, 2018 at 8:39 AM, Jean-Baptiste Onofré wrote: > No it's not (I'm testing the

Re: Merging Python code? Help avoid Python 3 regressions with these two simple steps :)

mpression it's blocked on infra? (e.g. it's > important but out of my hands). > > On Mar 1, 2018 11:05 PM, "Ahmet Altay" <al...@google.com> wrote: > >> I think we should prioritize the issue of installing Python 3 on the >> workers (https://issues.apache.org/jira/

Re: Merging Python code? Help avoid Python 3 regressions with these two simple steps :)

I think we should prioritize the issue of installing Python 3 on the workers (https://issues.apache.org/jira/browse/BEAM-3671). I would appreciate if folks pay attention to these 2 steps but I am worried that it will be easily forgotten. On Thu, Mar 1, 2018 at 6:51 PM, Holden Karau

Re: Instructions to install Python SDK from source

Hi Pablo, You have a great point. Getting started instructions for developers for Python SDK is not well documented. Installing Python SDK from source is a subset of this lack of documentation. There is a JIRA for this ( https://issues.apache.org/jira/browse/BEAM-3075). It would be great if you

Re: Python 3 flake 8: splitting up on the errors?

I think this is a great idea. I would encourage everyone who would like to help with Python 3 migration to help with this effort. Holden, if you already have a list, could you either share the list or create individual JIRAs so that we can track the work among us. On Tue, Feb 27, 2018 at 4:53 PM,

Re: Proposed improvements to our documentation

+1 I think this is a great idea, it can also serve as an inventory of where a language might be lacking in transforms and provide a good starting point for new contributors to fill in those gaps by looking at the existing Java implementations. On Wed, Feb 28, 2018 at 10:53 AM, Lukasz Cwik

Re: Python 3 reviewers

Thank you Holden for doing this work. I agree with Robert's comment. I know there are a few folks working on this now (you, @luke-zhu and @cclauss). Perhaps you could do python 3 related code reviews within that group. I would be happy to chime in and review some chunks as well. On Thu, Feb 22,

Re: [DISCUSS]: Beam 2.3.0 release archetypes missing mobile gaming examples

In my opinion waiting for the 2.4.0 release makes sense, since there is a plan to cut 2.4.0 release soon and this is examples and not a core function. In the meantime, we could add a notice to the website warning users about this issue and suggest them to use the previous release for trying out

Re: Beam 2.4.0

+1 for having regular release cycles. Finalizing a release takes time in the order of a few weeks and starting a new release soon after the previous one is a reliable way for having releases every 6 weeks. On Tue, Feb 20, 2018 at 2:30 PM, Robert Bradshaw wrote: > Yep. I am

Re: [VOTE] Release 2.3.0, release candidate #3

On Fri, Feb 16, 2018 at 9:52 PM, Jean-Baptiste Onofré wrote: > Hi, > > Can someone from Python grand me permission to upload Python SDK 2.3.0 to > PyPi ? > lukecwik, kennknowles, aljoscha, robertwb, davorbonaci are the package owners, any of them can do it. > > My user is

Re: [VOTE] Release 2.3.0, release candidate #3

+1 Thank you JB and thank you everyone for doing the validations. On Wed, Feb 14, 2018 at 5:24 PM, Eugene Kirpichov wrote: > Thanks Kenn. I retract my -1, but then someone must verify it with Flink > 1.4. I might give it a shot tomorrow (installing Flink 1.4 on Dataproc).

Re: Proposal: build Python wheel distributions for Apache Beam releases

+1 to wheels. The main effort for this would be updating the release guide, and adding support for other platforms in Jenkins for building and testing wheels. In light of this, maybe we can prioritize having test infrastructure for other platforms. On Mon, Feb 12, 2018 at 1:47 PM, Ismaël Mejía

Re: Off for 3 weeks

Best wishes, hope you will recover quickly. On Mon, Feb 12, 2018 at 9:03 AM, Kenneth Knowles wrote: > Best wishes for a swift recovery. > > Kenn > > > On Sat, Feb 10, 2018 at 5:56 AM, Etienne Chauchot > wrote: > >> Hi guys, >> >> I've been off this week

Re: [VOTE] Release 2.3.0, release candidate #2

+1 I verified python quick start, mobile gaming examples, streaming on Direct and Dataflow runners. Thank you JB! On Thu, Feb 8, 2018 at 2:27 AM, Romain Manni-Bucau wrote: > +1 (non-binding), thanks JB for the effort! > > > Romain Manni-Bucau > @rmannibucau

Re: Replacing Python DirectRunner apply_* hooks with PTransformOverrides

+1 to this change. Thank you Charles for improving the DirectRunner, sharing your progress and seeking feedback. This change would allow us to migrate to a faster DirectRunner for Python. A long time requested feature and an important part of the first use experience for new users trying out

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

This will require a change in the Beam code, because image names are hardcoded in to code (python) and configuration (java). RC1 as it is will not work correctly with Cloud Dataflow. On Wed, Jan 31, 2018 at 2:08 PM, Reuven Lax wrote: > Hopefully we can validate soon. I believe

Re: Does Apache Beam for python support server-based shuffle with Dataflow runner yet?

Hi Nima, You can try this feature with python SDK using the same instructions from the announcement. However, it is not ready for production usage. Team is working official supporting it. We cannot share an ETA, once it is available it will be announced. For future questions related to the

Re: Pushing daily/test containers for python

not guaranteed to work with any other >>>> version. Breaking changes in their interaction would cause confusion and >>>> create noise. Any local tests can also in theory just build the container >>>> images directly and not use any registry, so it might make se

Re: A question regarding BEAM-3280

this problem. I could not assign to you. (I guess you first need to be added as a contributor to the project). I added comment mentioning that you are working on this issue. Thank you again! Ahmet > > Regards, > Norio Akagi > > > On Dec 11, 2017, at 4:50 PM, Ahmet Altay

Re: [jira] [Commented] (BEAM-3357) Python SDK head fails to run tests due to Requirement.parse('protobuf<=3.4.0,>=3.2.0')

te: > > +1 to pinning to exact versions, to be sure that our releases do not > break > > when newer versions of dependencies are released. > > > > On Fri, Dec 15, 2017 at 2:44 PM Ahmet Altay <al...@google.com> wrote: > >> > >> On Fri, Dec 15, 2017 at

Re: [jira] [Commented] (BEAM-3357) Python SDK head fails to run tests due to Requirement.parse('protobuf<=3.4.0,>=3.2.0')

other hand it will prevent breaking of already released versions. > > Thanks, > Cham > > On Fri, Dec 15, 2017 at 2:19 PM Ahmet Altay <al...@google.com> wrote: > >> On Fri, Dec 15, 2017 at 2:02 PM, Robert Bradshaw <rober...@google.com> >> wrote: >>

Re: [jira] [Commented] (BEAM-3357) Python SDK head fails to run tests due to Requirement.parse('protobuf<=3.4.0,>=3.2.0')

On Fri, Dec 15, 2017 at 1:38 PM, Robert Bradshaw wrote: > I am also in favor of pinning as an immediate fix, bumping the bound > otherwise. > > Regarding putting an upper bound to avoid being broken, the last two > breaks have been due to just having an (unneeded) upper

Re: A personal update

Welcome back! Looking forward to your contributions. Ahmet On Tue, Dec 12, 2017 at 10:05 PM, Jesse Anderson wrote: > Congrats! > > On Wed, Dec 13, 2017, 5:54 AM Jean-Baptiste Onofré > wrote: > >> Hi Davor, >> >> welcome back !! >> >> It's really

Re: A question regarding BEAM-3280

Hi Norio, Thank you for your interest. If you would like to work on this I can assign the JIRA to you. I do not think this change in sufficient or correct. This reads as if SplitLinesToWordsFn returns a Tuple of things, however instead it produces three unrelated collections of different types.

Re: Apache Beam, version 2.2.0

On Thu, Dec 7, 2017 at 3:51 PM, Eugene Kirpichov wrote: > I've sent the poll https://lists.apache.org/thread.html/ > 5bc2e184a24de9dbc8184ffd2720d1894010497d47d956b395e037df@% > 3Cuser.beam.apache.org%3E > Will figure out how to tweet from @ApacheBeam, and sent the Twitter

Re: Apache Beam, version 2.2.0

Thank you Reuven! I tweeted the release announcement on Beam's account. On Mon, Dec 4, 2017 at 9:49 PM, Reuven Lax wrote: > Technically it's a backwards-incompatible change, however if we are > convinced the risk is low we could do it. > > As mentioned on the original thread,

Re: [DISCUSS] Thinking about Beam 3.x roadmap and release schedule

My wishlist for 2018 would be - Python 3 support - Python SDK to work with more runners. This is covered in portability in general. I would like to see an enterprise grade Python SDK that can run on a range of Beam runners. - Related to the above item, full streaming support with Python SDK. -

Re: Version 2.2.0 release date

Hi Stefania, Release candidate for 2.2.0 is currently being voted [1]. The release will happen after a successful vote. Ahmet [1] https://lists.apache.org/thread.html/da2acabdb15c9f8d11351f9167633a 4b089664fe3cce014ba619c937@%3Cdev.beam.apache.org%3E On Mon, Nov 20, 2017 at 7:04 AM, Stefania

Re: Python SDK DirectRunner (new feature)

Thank you María. On Mon, Nov 20, 2017 at 5:31 PM, María García Herrero < mari...@google.com.invalid> wrote: > Hello, > > I recently worked on adding a bundle retry for the Python SDK DirectRunner > ( > https://issues.apache.org/jira/browse/BEAM-2718). > > The goal was to have a more reliable

Re: HDFS Support for Python SDK

Thank you Udi, this is a great comparison of available options. On Mon, Nov 20, 2017 at 5:26 PM, Udi Meiri wrote: > Hi, > > I've done some research into implementing HDFS support for Python SDK and > I'd like your input. This work is regarding BEAM-3099 >

Re: [VOTE] Release 2.2.0, release candidate #4

+1 I verified the python quick start on Windows. I could not verify the documentation changes because the staged version expired. On Mon, Nov 20, 2017 at 12:08 PM, Eugene Kirpichov < kirpic...@google.com.invalid> wrote: > Thanks Luke. I was able to validate quickstart on Dataflow and on Spark

Re: python3 support schedule

For reference https://issues.apache.org/jira/browse/BEAM-1251 is the umbrella issue tracking python3 support in the core SDK. There needs to be additional runner specific work (e.g. DataflowRunner needs to use python3 binary on its workers) once the core work is completed. Ahmet On Thu, Nov 2,

Re: [DISCUSS] Move away from Apache Maven as build tool

Has anyone started a POC with Bazel? I would be interested in helping that effort. On Wed, Nov 1, 2017 at 9:27 AM, Lukasz Cwik wrote: > I have started a POC for using Gradle here: > https://github.com/lukecwik/incubator-beam/tree/gradle > > Things that work: > *

Re: [Proposal] Sharing Neville's post and upcoming meetups in the Twitter handle

Done. On Thu, Oct 26, 2017 at 11:26 AM, Griselda Cuevas wrote: > Hi folks, could you help us to tweet the second part of Neville's blogpost? > > Here's a suggested tweet: > 2nd part of @sinisa_lyh's post is out! Read how @Spotify developed Scio, a > high level Scala API 4 the

Re: [Proposal] Sharing Neville's post and upcoming meetups in the Twitter handle

This makes sense to me. I published the first tweet, we can publish the second one perhaps closer to the event. Ahmet On Fri, Oct 20, 2017 at 1:08 PM, Griselda Cuevas wrote: > Hi everyone - What do you think about sharing Neville's blogpost[1] about > the road to Scio

Re: New contributor

Welcome Vilhem! On Wed, Oct 18, 2017 at 4:55 AM, Etienne Chauchot wrote: > Welcome! > > > > Le 17/10/2017 à 22:18, Vilhelm von Ehrenheim a écrit : > >> Hi everyone! >> My name is Vilhelm von Ehrenheim and I would like to start contributing to >> Beam. >> I work as a Data

Re: Problem while upgrading lib

google-apitools dependency (which is required for GCS) does not work with oauth2client >= 4.0.0 [1]. Because of this Beam Python SDK also does not work with oauth2client >= 4.0.0 versions, and this is captured correctly in the setup.py [2]. Ahmet [1]

Ahmet offline for the next 3 weeks

Hi all, I will be on vacation starting tomorrow through first week of October. I would not be able to respond to most of the things. Happy Beaming, Ahmet

Re: Merge branch DSL_SQL to master

+1 Thanks to all contributors/reviewers! On Thu, Sep 7, 2017 at 9:55 AM, Kai Jiang wrote: > +1 looking forward to this. > > On Thu, Sep 7, 2017, 09:53 Tyler Akidau > wrote: > > > +1, thanks for all the hard work to everyone that contributed! > >

Re: [RESULT][VOTE] Release 2.1.0, release candidate #3

On Tue, Aug 22, 2017 at 5:12 PM, Ahmet Altay <al...@google.com> wrote: > I believe this release is complete now. Thank you JB for pushing this > release, and everyone else who contributed to it. > > On Tue, Aug 22, 2017 at 4:26 PM, Ahmet Altay <al...@google.com> wro

Re: [RESULT][VOTE] Release 2.1.0, release candidate #3

I believe this release is complete now. Thank you JB for pushing this release, and everyone else who contributed to it. On Tue, Aug 22, 2017 at 4:26 PM, Ahmet Altay <al...@google.com> wrote: > Remaining items for closing this release are: > - Move source distribution from de

Re: [RESULT][VOTE] Release 2.1.0, release candidate #3

Remaining items for closing this release are: - Move source distribution from dev repository to release repository in dist.apache.org - Finalize the version in JIRA. - Announce on user@ and other places. On Tue, Aug 22, 2017 at 2:18 PM, Ahmet Altay <al...@google.com> wrote: > > >

Re: [RESULT][VOTE] Release 2.1.0, release candidate #3

On Tue, Aug 22, 2017 at 2:07 PM, Ahmet Altay <al...@google.com> wrote: > > > On Tue, Aug 22, 2017 at 12:08 PM, Ahmet Altay <al...@google.com> wrote: > >> >> >> On Tue, Aug 22, 2017 at 10:59 AM, Ahmet Altay <al...@google.com> wrote: >> >

Re: [RESULT][VOTE] Release 2.1.0, release candidate #3

On Tue, Aug 22, 2017 at 12:08 PM, Ahmet Altay <al...@google.com> wrote: > > > On Tue, Aug 22, 2017 at 10:59 AM, Ahmet Altay <al...@google.com> wrote: > >> Thank you JB. >> >> On Mon, Aug 21, 2017 at 11:33 PM, Jean-Baptiste Onofré <j...@nanthrax.net&

Re: [RESULT][VOTE] Release 2.1.0, release candidate #3

On Tue, Aug 22, 2017 at 10:59 AM, Ahmet Altay <al...@google.com> wrote: > Thank you JB. > > On Mon, Aug 21, 2017 at 11:33 PM, Jean-Baptiste Onofré <j...@nanthrax.net> > wrote: > >> Hi >> >> This vote passed with only +1. >> >> I'm promoting

Re: [RESULT][VOTE] Release 2.1.0, release candidate #3

gt;> >> > >>> >>> Hi, > >>> >>> > >>> >>> Spark runner was tested with word count example and a more > >>complex > >>> session > >>> >>> based application on a yarn cluster. > >&g

Re: Policy for stale PRs

certainly reasonable; 30 might be too > > > short) if the author has not responded to actionable feedback. > > > > > > On Wed, Aug 16, 2017 at 12:07 PM, Sourabh Bajaj < > > > sourabhba...@google.com.invalid> wrote: > > > > > >> Some proje

Re: Policy for stale PRs

> JB > > > > On Aug 15, 2017, 01:29, at 01:29, Ted Yu <yuzhih...@gmail.com> wrote: > > >The proposal makes sense. > > > > > >If the author of PR doesn't respond for 90 days, the PR is likely out > > >of > > >sync with current repo. >

Re: Hello from a newbie to the data world living in the city by the bay!

Welcome both of you! Some helpful starting points: - Contribution guide [1] - Unassigned starter issues in JIRA [2] Ahmet [1] https://beam.apache.org/contribute/contribution-guide/ [2]

Re: [VOTE] Release 2.1.0, release candidate #3

On Mon, Aug 14, 2017 at 6:32 AM, Ismaël Mejía wrote: > +1 (non-binding) > > - Validated signatures OK > - mvn clean verify -Prelease on both OpenJDK 1.7 and Oracle JDK 8 with > the docker development images (WIP), both OK > - Run WordCount on local Flink and Spark runners OK >

Re: [ANNOUNCEMENT] New committers, August 2017 edition!

Congratulations to all of you. Well deserved and thank you for your contributions. On Fri, Aug 11, 2017 at 10:43 AM, tarush grover wrote: > Congratulations!! > > Regards, > Tarush > > On Fri, 11 Aug 2017 at 11:11 PM, Davor Bonaci wrote: > > > Please

Re: [VOTE] Release 2.1.0, release candidate #3

+1, Thank you JB! - I verified the hashes for apache-beam-2.1.0-python.zip, apache-beam-2.1.0-source-release.zip files - Unzipped apache-beam-2.1.0-source-release.zip and ran python packaging and unittests using tox - Ran python wordcount and mobile gaming examples with DirectRunner and

Re: [INFO] Build fails on master

Hey, are you referring to a specifc Jenkins build? If not could you share the actual error? Last python post commit test was successful ( https://builds.apache.org/view/A-D/view/Beam/job/beam_PostCommit_Python_Verify/2887/), although the one before that failed. The failure looks like a flaked to

Re: [DISCUSS] Beam pipeline logical and physical DAGs visualization.

+1, this looks great and it will be very useful for users to understand their pipelines. On Thu, Aug 3, 2017 at 8:25 PM, Pei HE wrote: > Hi all, > While working on JStorm and MapReduce runners, I found that it is very > helpful to understand Beam pipelines by visualizing them.

Re: [VOTE] Release 2.1.0, release candidate #2

Jean-Baptiste Onofré <j...@nanthrax.net> >> wrote: >> >> So, I guess you are voting +1 on RC2, correct (just for the tracking) ? >>> >>> Thanks, >>> Regards >>> JB >>> >>> On 07/19/2017 08:00 AM, Ahmet Altay wrote: >>> &

Re: [VOTE] Release 2.1.0, release candidate #2

Thank you JB. I validated python wordcount and mobile gaming examples on Linux. Found one issue (https://issues.apache.org/jira/browse/BEAM-2636). This does not need to be a blocking issue for RC2, but if we end up having a RC3 we should consider fixing this issue. Ahmet On Tue, Jul 18, 2017 at

Re: [CANCEL][VOTE] Release 2.1.0, release candidate #1

On Mon, Jul 17, 2017 at 5:08 AM, Jean-Baptiste Onofré wrote: > Hi all, > > as discussed, I cancel the vote on RC1 in order to prepare a RC2. > > The RC2 should include the following fixes: > > - BEAM-2595 is already fixed and cherry-picked on release-2.1.0 branch > - BEAM-2271

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

tion to check to open Jira on the release > > target. I > > just missed these two Jira, sorry about that. > > > > I don't think an additional list is required. > > > > I will cancel this vote and cut a RC2 as soon as BEAM-2595 and BEAM-2771 > > are > > add

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

-1 Thank you JB. Unfortunately I do not want to approve this RC :(. My reason is that there are two open issues in the burndown list ( https://s.apache.org/beam-2.1.0-burndown). I think we should either fix them or explicitly move them out of the list. BEAM-2595 is a regression in usability (not

Re: Passing pipeline options into PTransforms and Filesystems in Python

+1 to the above responses to for passing option into PTransforms. As Robert mentioned in the JIRA issue, filesystem plug-ins are in a different category. It is reasonable for them to create credentials based on options/environment variables. We could have a protocol for instantiating file system

Re: Mixed-Language Pipelines

Thank you Thomas. I think this will especially be great for Python SDK, allowing it to tap into many sources that exist in the Java SDK. I added my comments. Ahmet On Mon, Jul 10, 2017 at 9:58 AM, Thomas Groh wrote: > Hey everyone; > > I've been working on a design

Re: [Proposal] Submitting pipelines to Runners in another language

Thank you Sourabh. I added my comments as well and +1 to Kenn. On Thu, Jul 6, 2017 at 2:21 PM, Kenneth Knowles wrote: > I added a few detailed comments. I definitely think we should move forward > on this to get Python pipelines running on all our our runners, and >

Re: [DISCUSS] Apache Beam 2.1.0 release next week ?

+1 For Python, there are 2 hard blocking issues (and 2 nice to haves) all tagged as blocking 2.1.0 [1]. Ahmet [1]

Re: Windows OS Compatibility and Jenkins Postcommit

Thank you Luke, this is great! I hope that we will see a mac version of this at some point. It looks like there is no python binary and python tests are failing for that. Ahmet On Thu, Jun 8, 2017 at 3:55 PM, Flavio Fiszman wrote: > Thanks Luke! I'm working on

Re: Build failed in Jenkins: beam_PostCommit_Java_MavenInstall #3982

Thank you Kenn. https://github.com/apache/beam/pull/3278 is for fixing the lint errors, On Thu, Jun 1, 2017 at 11:11 AM, Kenneth Knowles wrote: > On the surface, it looks like Python lint failed, but I failed after a few > seconds to track down the actionable error message. >

Re: low availability in the coming 4 weeks

Congratulations! On Thu, May 25, 2017 at 10:54 AM, Jean-Baptiste Onofré wrote: > Congrats and enjoy ! > > Regards > JB > > > On 05/25/2017 05:33 AM, Mingmin Xu wrote: > >> Hello everyone, >> >> I'll take 4 weeks off to take care of my new born baby. I'm very glad that >>

Re: First stable release completed!

Congratulations everyone, this is great! On Wed, May 17, 2017 at 7:26 AM, Kenneth Knowles wrote: > Awesome. A huge step. > > On Wed, May 17, 2017 at 6:30 AM, Andrew Psaltis > wrote: > > > This is fantastic. Great job! > > On Wed, May 17, 2017

Re: First stable release: version designation?

I would also like to vote for strong 2.0 with the same reasons as Dan mentioned. It will be less confusing for the users overall. Ahmet On Fri, May 5, 2017 at 9:33 AM, Davor Bonaci wrote: > Strongly for 2.0.0: > * Aljoscha > * Cham > * Dan > * Luke > > Slight preference

Re: Congratulations Davor!

Congratulations, well deserved! On Thu, May 4, 2017 at 10:35 AM, Andrew Psaltis wrote: > Congrats Davor! > > On Thu, May 4, 2017 at 1:34 PM, Melissa Pashniak < > meliss...@google.com.invalid> wrote: > > > Congratulations Davor! > > > > > > On Thu, May 4, 2017 at 10:32

Re: Community hackathon

+1, this is a great idea. On Mon, Apr 24, 2017 at 3:54 AM, JingsongLee wrote: > +1 > best, > Jingsonglee > --From:Ted > Yu Time:2017 Apr 24 (Mon) 17:29To:dev < >

Re: Python build artifacts seem to be misconfigured

if it can be configured that all (or, as many as > possible) build-generated files use one specific directory -- "target/". > Likely, all problems would just go away. > > On Wed, Apr 12, 2017 at 3:24 PM, Ahmet Altay <al...@google.com.invalid> > wrote: > &g

Re: Python build artifacts seem to be misconfigured

This is also root cause for the flakiness in test_using_slow_impl very flaky locally tests (https://issues.apache.org/jira/browse/BEAM-1910). Kenn, have you found anything that might explain why tox is not deleting them? Ahmet On Tue, Apr 11, 2017 at 11:50 AM, Robert Bradshaw <

Re: [DISCUSSION] Consistent use of loggers

On Wed, Mar 22, 2017 at 10:38 AM, Tibor Kiss wrote: > This is a great idea! > > I believe Python-SDK's logging could also be enhanced (a bit differently): > Currently we are not instantiating the logger, just using the class what > logging package provides. > Shortcoming

Re: [ANNOUNCEMENT] New committers, March 2017 edition!

Congratulations to all you! On Fri, Mar 17, 2017 at 4:28 PM, Chamikara Jayalath wrote: > Thanks all. Congrats to other new committers !! > > I'm very excited to join. > > - Cham > > On Fri, Mar 17, 2017 at 3:02 PM Mark Liu > wrote: > > >

Re: [RESULT] [VOTE] Release 0.6.0, release candidate #2

Excellent! > > On Wed, Mar 15, 2017, 6:13 AM Jean-Baptiste Onofré <j...@nanthrax.net> > wrote: > > > Hi Ahmet, > > > > it seems Jira is not up to date: 0.6.0 version is not flagged as > > "Released". > > > > Can you fix that please ? > &

Re: [RESULT] [VOTE] Release 0.6.0, release candidate #2

amazing! Ahmet On Tue, Mar 14, 2017 at 2:22 PM, Ahmet Altay <al...@google.com> wrote: > I'm happy to announce that we have unanimously approved this release. > > There are 7 approving votes, 4 of which are binding: > * Aljoscha Krettek > * Davor Bonaci > * Ismaël Mejía

[RESULT] [VOTE] Release 0.6.0, release candidate #2

I'm happy to announce that we have unanimously approved this release. There are 7 approving votes, 4 of which are binding: * Aljoscha Krettek * Davor Bonaci * Ismaël Mejía * Jean-Baptiste Onofré * Robert Bradshaw * Ted Yu * Tibor Kiss There are no disapproving votes. Thanks everyone! Ahmet

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

t; > > > > wrote: > > > > > > > > +Stas Levin <stasle...@apache.org> +Thomas Groh <tg...@google.com> > > > > > > > > On Mon, Mar 13, 2017 at 5:30 PM Eugene Kirpichov < > kirpic...@google.com > > > > > > &g

<    4   5   6   7   8   9   10   >