Re: Contributor permission for Jira tickets

Done. Welcome. On Thu, Mar 25, 2021 at 3:39 AM Fabien Caylus wrote: > Hi ! > > I'm sorry for this second message. But I realized that my first one was > detected as spam by gmail, because I used the Pony Mail interface to send > it ... > So I believed it may have been detected as spam for others

Re: Hi Team

Welcome Uday! On Mon, Mar 29, 2021 at 11:23 AM Uday Singh wrote: > Hi Everyone, > > This is Uday and i will be working on Apache Beam from GCP dataflow team. > Looking forward to contributing to the community. > > Thanks > Uday >

Re: [Apace BEAM Go improvements] Lazy map side inputs

Adding some folks who might be able to help: @Robert Burke @Kenneth Knowles @Tyson Hamilton On Mon, Mar 29, 2021 at 2:31 PM Miguel Anzo Palomo wrote: > Hi, > I was checking out this task BEAM-3293 > and I'm having some > issues fully understa

Re: [DISCUSS] Jira isssue type: "Support"

+1 on using a label instead. I think the naming will matter. "Support" might send a wrong message, but "User Issue" sounds more neutral and would necessarily set an expectation to receive support. (I have no data to "support" this :), it is a guess.) Would it be possible to somehow link user@ list

Re: [ANNOUNCE] New committer: Tomo Suzuki

Congratulations! 🎉🎉🎉 On Fri, Apr 2, 2021 at 9:38 AM Kenneth Knowles wrote: > Hi all, > > Please join me and the rest of the Beam PMC in welcoming a new committer: > Tomo Suzuki > > Since joining the Beam community in 2019, Tomo has done lots of critical > work on Beam's dependencies: maintaining

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] https://issues.apache.org/jira/browse/BEAM-3844?jql=project%20%3D%20BEAM%20AND%20status%20in%20(Open%2C%20Reopened)%20AND%20resolution%20%3D%20U

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 on

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 wrote: > +1 Thank you Robert. > > Verified python mobile gaming examples using the wheel files on direct > runner. Got user_score

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 proposal only concern

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: [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 proposal to add an ex

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: https://builds.apach

Re: How to decide how much quota do I need

+ user, dev to bcc Eila, there is some information here: https://cloud.google.com/dataflow/quotas on quotas in general. Specifically for in use IP addresses, you can look at autoscaling messages and see what was autoscaling trying to upscale to. It is also possible to use large machine types (e.g

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: 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é wrote: > Hi Eila, >

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: [PROPOSAL] Python 3 support

ubpackage. >> 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. > +1 updating tox.ini and adding new checks to run_

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 newly >> elected members of the Apache Sof

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 but not merging win

Re: [PROPOSAL] Python 3 support

ts >>>>> unwieldy, perhaps a spreadsheet with modules/packages on one axis and the >>>>> various automated/manual conversions along the other would be helpful? >>>>> >>>>> A note on automated tools, they're sometimes overly conservat

Re: [PROPOSAL] Preparing 2.5.0 release next week

+1 to delaying 2 weeks. I think it will be prudent to wait in this case. There is too much in flux with Gradle migration currently and based on Scott's latest update I think we will be in a more stable state in 2 weeks. Last Beam release date was 3/20 and our plan was to make a release every 6 wee

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

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 wrote: > I had a similar problem. > > On Fri, Apr 6, 2018, 6:23 PM Ahmet Altay wrote: > >> I tried to crea

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 cont

Re: [PROPOSAL] Python 3 support

to myself? > And edit rights to the Kanban board? > > Robbe > > On Tue, 17 Apr 2018 at 22:56 Ahmet Altay wrote: > >> Kanban board for python 3: https://issues.apache.org/ >> jira/secure/RapidBoard.jspa?rapidView=245 >> >> (Thank you Davor!) >> >>

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 for

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, Jean-Bap

Re: [PROPOSAL] Preparing 2.5.0 release next week

a release blocker, could you please add it to the list? > > Just an FYI. Since the fix is likely small fixes to build file it seems ok > to cut the branch and cherry pick. > > Kenn > > On Thu, May 17, 2018, 17:41 Ahmet Altay wrote: > >> Hi JB and all, >> >>

Re: [VOTE] Go SDK

+1 (binding) Congratulations to the team! On Tue, May 22, 2018 at 10:13 AM, Alan Myrvold wrote: > +1 (non-binding) > Nice work! > > On Tue, May 22, 2018 at 9:18 AM Pablo Estrada wrote: > >> +1 (binding) >> Very excited to see this! >> >> On Tue, May 22, 2018 at 9:09 AM Thomas Weise wrote: >>

Re: [PROPOSAL] Preparing 2.5.0 release next week

ieve JB is referring >> > to https://issues.apache.org/jira/browse/BEAM-4060 >> > >> > On Fri, May 18, 2018 at 10:16 AM Scott Wegner > > <mailto:sweg...@google.com>> wrote: >> > >> > J.B., can you give any

Re: Hello Beam!

Welcome Rui! On Tue, May 29, 2018 at 2:49 PM, Rui Wang wrote: > Hi there, > > I am Rui (pronounced as same as "Ray")! > > I recently joined Google Cloud. Beam is a very interesting project and I > cannot wait to contribute to it! > > > Thanks, > Rui >

Re: [PROPOSAL] Preparing 2.5.0 release next week

issue about ParquetIO on HDFS/S3 that I would like to > investigate with the team. > Do you know who is currently investigating the ParquetIO issue? Do you need help with that? > > I plan to start the release process asap, hopefully later today. > > Regards > JB > >

Re: [ANNOUNCEMENT] New committers, May 2018 edition!

Congratulations to all of you! On Thu, May 31, 2018 at 7:26 PM, Chamikara Jayalath wrote: > Congrats to all three!! > > On Thu, May 31, 2018 at 7:09 PM Davor Bonaci wrote: > >> Please join me and the rest of Beam PMC in welcoming the following >> contributors as our newest committers. They have

Re: [VOTE] Use probot/stale to automatically manage stale pull requests

+1 On Fri, Jun 1, 2018, 9:32 AM Jason Kuster wrote: > +1 (non-binding): automating policy ensures it is applied fairly and > evenly and lessens the load on project maintainers; hearty agreement. > > On Fri, Jun 1, 2018 at 9:25 AM Alan Myrvold wrote: > >> +1 (non-binding) I updated the pull requ

Re: [VOTE] Code Review Process

+1 On Fri, Jun 1, 2018 at 10:37 AM, Kenneth Knowles wrote: > +1 > > On Fri, Jun 1, 2018 at 10:25 AM Thomas Groh wrote: > >> As we seem to largely have consensus in "Reducing Committer Load for Code >> Reviews"[1], this is a vote to change the Beam policy on Code Reviews to >> require that >> >>

Re: [VOTE] Policies for managing Beam dependencies

+1 Thank you for driving these decisions. I would make a meta-point, all other recent votes and if passes this one could be converted to web site documents at some point in an easily accessible and linkable way. On Wed, Jun 6, 2018 at 4:53 PM, Chamikara Jayalath wrote: > Hi All, > > We recently

Re: [VOTE] Policies for managing Beam dependencies

I think this is relevant for users. It makes sense for users to know about how Beam work with its dependencies and understand how conflicts will be addressed and when dependencies will be upgraded. On Mon, Jun 11, 2018 at 9:09 PM, Kenneth Knowles wrote: > Do you think this has relevance for user

Re: [VOTE] Apache Beam, version 2.5.0, release candidate #1

Thank you JB. For the wheel artifacts, Boyuan was trying to get the instructions from Robert and reproduce the artifacts. She can help you with this if you need. Ahmet On Mon, Jun 11, 2018 at 10:29 PM, Jean-Baptiste Onofré wrote: > Hi, > > sorry, I missed wheel artifact. Something to add on th

Re: [CANCEL][VOTE] Apache Beam, version 2.5.0, release candidate #1

Ismaël, I believe Pablo's https://github.com/apache/beam/pull/5609 is fixing the issue by changing the findbugs back to "com.github.stephenc.findbugs". Is this what you are referring to? Ahmet On Tue, Jun 12, 2018 at 2:51 PM, Boyuan Zhang wrote: > Hey JB, > > I added some instructions about ho

Re: Beam Dependency Check Report (2018-06-13)

Thanks Yifan, this is great! My unsolicited feedback: - Could it warn against dependencies that did not get updates for a long time? For python there were examples of a dependency being abandoned by its own developers and it took us a while to figure it out and switch to maintained one. (Currently

Re: [CANCEL][VOTE] Apache Beam, version 2.5.0, release candidate #1

bugs-annotations/releases >>>>>> [3] https://github.com/apache/beam/pull/5609/commits/ >>>>>> 32c7df706e970557f154ff6bc521b2e00f9d09ab >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>

Re: Proposal: keeping post-commit tests green

On Wed, Jun 13, 2018 at 3:45 PM, Mikhail Gryzykhin wrote: > Hello everybody, > > Thanks everyone. I didn't receive any more feedback on the design proposal > document [1] and I believe we've reached consensus. I've added > implementation tasks in JIRA (BEAM-4559 [2]) and will start coding soon.

Re: Proposal: keeping post-commit tests green

On Wed, Jun 13, 2018 at 3:52 PM, Mikhail Gryzykhin wrote: > Hi Ahmet, > > I've checked on tests status and most of other tests are green 98% of the > time. So I feel that we do not need any explicit actions for those tests. > Is it going to be a one time action to fix existing flaky tests? Or is

Re: Proposing interactive beam runner

Thank you Sindy. I like the demo; it looks great. This would be interesting to a lot of users. What are your plans for moving this forward? What kind of an input you are looking for? Ahmet On Wed, Jun 13, 2018 at 2:32 PM, Eugene Kirpichov wrote: > This is awesome, thanks Sindy! I hope that the

Re: [DISCUSS] Releasing Beam in the presence of emergencies

Thank you Rafael. I think it is a good idea to include our commitment, including concrete steps on our website. This would make it easier for enterprise users to choose Beam. Even though this is already partially Apache policy and there is precedence in our project with 2.1.1 release; increasing t

Re: [PROPOSAL] Merge samza-runner to master

Thank you for everyone who contributed to this runner. It is really great to see this. Xinyu, for the people like myself who were not following the development closely, could you talk about missing pieces, work in progress, future plans? On Mon, Jun 18, 2018 at 3:37 PM, Rafael Fernandez wrote:

Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2

I support Kenn's proposal of removing binary artifacts and otherwise keeping the RC2. We have done it in the pas with similar binary files that were unintended. At the same time, it will follow the suggestion from LEGAL-288. As a follow up we can build this removal into our release process until th

Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2

nch with that > exclusion: https://github.com/pabloem/incubator-beam/ > archive/v2.5.0-TEST-ARCHIVE.zip > Best > -P. > > On Wed, Jun 20, 2018 at 11:00 AM Ahmet Altay wrote: > >> I support Kenn's proposal of removing binary artifacts and otherwise >> keeping the

Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2

I already voted a +1 2 days ago. Again: +1 (binding) Thank you JB! On Fri, Jun 22, 2018 at 9:23 AM, Alan Myrvold wrote: > The https://dist.apache.org/repos/dist/dev/beam/2.5.0/ > apache-beam-2.5.0-source-release.zip still contains > the beam-release-2.5.0/gradle/wrapper/gradle-wrapper.jar. Do

Re: [PROPOSAL] Add a blog post for Beam release 2.5.0

Thank you Alexey! It is a great idea. I added my suggestions to the doc. On Fri, Jun 22, 2018 at 1:01 PM, Alexey Romanenko wrote: > Hi everyone, > > I propose to continue a tradition of publishing new blog post for Beam web > site (as it was positively accepted by community before) with announc

Re: [RESULT][VOTE] Apache Beam, version 2.5.0, release candidate #2

>> Regards >> JB >> >> On 23/06/2018 05:17, Jean-Baptiste Onofré wrote: >> > Hi all, >> > >> > I'm happy to announce that we have unanimously approved this release. >> > >> > There are 12 approving votes, 5 of which are binding: >&g

Re: [RESULT][VOTE] Apache Beam, version 2.5.0, release candidate #2

On Mon, Jun 25, 2018 at 10:49 AM, Ahmet Altay wrote: > JB, thank you for making this release happen. > > I noticed that python artifacts are not deployed to pypi yet. Would you > like me to do that? > > Thank you, > Ahmet > > On Sat, Jun 23, 2018 at 6:45 AM, Rafael Fer

Re: [RESULT][VOTE] Apache Beam, version 2.5.0, release candidate #2

; a asfbot merge this morning). > > Regards > JB > > On 25/06/2018 19:49, Ahmet Altay wrote: > > JB, thank you for making this release happen. > > > > I noticed that python artifacts are not deployed to pypi yet. Would you > > like me to do that? > > > &

Re: [RESULT][VOTE] Apache Beam, version 2.5.0, release candidate #2

Beam site pull request is merged. JB, please send release announcement whenever it is convenient for you. Thank you again! Ahmet On Mon, Jun 25, 2018 at 10:39 PM, Ahmet Altay wrote: > Thank you JB! > > On Mon, Jun 25, 2018 at 10:34 PM, Jean-Baptiste Onofré > wrote: > >&

Re: [DISCUSS] Automation for Java code formatting

+1 This is great idea. Does anyone know a similar tool for python? I believe go already has this as part of its tools with go fmt. On Tue, Jun 26, 2018 at 9:55 PM, Ankur Goenka wrote: > +1 > > Intellij can help but still formatting is an additional thing to keep in > mind. Enabling auto format

Re: Using user developped source in streamline python

Hi Sébastien, Currently there is no work in progress for including the write transforms for the locations you listed. You could develop your own version if interested. Please see WriteToBigquery transform [1] for reference. Ahmet [1] https://github.com/apache/beam/blob/375bd3a6a53ba3ba7c965278dc

Re: Filtered Pre-commit triggering is BACK!

Two of my PRs with python changes did not trigger any pre-commits. Could it be related to this change? https://github.com/apache/beam/pull/5768 https://github.com/apache/beam/pull/5800 Ahmet On Tue, Jun 26, 2018 at 2:30 PM, Andrew Pilloud wrote: > Awesome! This will save so much time running

Re: Samza runner committer support

I would be happy to help with this. I can prioritize python related changes. For portability related changes I can try to help but I may not be the best person. On Thu, Jun 28, 2018 at 12:33 PM, Xinyu Liu wrote: > Hi, All, > > Our Samza runner has recently been merged to master, and Kenn has bee

Re: Help! Beam SQL needs more committer support

I am also happy to happy to help and interested in learning more about Beam SQL. On Thu, Jun 28, 2018 at 11:53 AM, Kai Jiang wrote: > I am very interested in supporting SQL PRs to help you reduce your > bandwidths. > > Best, > Kai > > > On Thu, Jun 28, 2018, 11:52 Austin Bennett > wrote: > >> S

Re: [Design Proposal] Improving Beam code review

Thank you Huygaa. This document looks good to me. I think auto-assigning PRs could significantly help especially with first time contributors. It could also give us a chance to distribute reviews in a more balanced way across committers. On Thu, Jun 28, 2018 at 7:37 AM, Alexey Romanenko wrote: >

Re: [PROPOSAL] Prepare Beam 2.6.0 release

Sounds reasonable to me. Thank you Pablo. For reference, list of open issues marked for 2.6.0 [1]. It is a good time to look at this list and add/remove issues as needed. [1] https://issues.apache.org/jira/browse/BEAM-4417?jql=project%20%3D%20BEAM%20AND%20resolution%20%3D%20Unresolved%20AND%20fix

Re: CODEOWNERS for apache/beam repo

+1 I added my name and a few others names that frequently do reviews in some areas. On Tue, Jul 10, 2018 at 10:23 AM, Jean-Baptiste Onofré wrote: > +1 > > I added my name on some components ;) > > Thanks ! > Regards > JB > > On 10/07/2018 02:06, Udi Meiri wrote: > > Hi everyone, > > > > I'm pro

Re: [ANNOUNCEMENT] Nexmark included to the CI

Thank you Etienne! This looks great. I hope we can get other languages to have benchmarks at this level soon enough. Ahmet On Thu, Jul 12, 2018 at 1:45 PM, Ismaël Mejía wrote: > That’s great to see in action, great work Etienne! > > Is there any document on how to integrate ‘stuff’ into the da

Re: [PROPOSAL] Prepare Beam 2.6.0 release

On Fri, Jul 13, 2018 at 10:48 AM, Pablo Estrada wrote: > Hi all, > I've triaged most issues marked for 2.6.0 release. I've localized two that > need a decision / attention: > > - https://issues.apache.org/jira/browse/BEAM-4417 - Bigquery IO Numeric > Datatype Support. Cham is not available to fix

Re: Automatically create JIRA tickets for failing post-commit tests

This proposal looks good to me. On Fri, Jul 13, 2018 at 10:49 AM, Jason Kuster wrote: > I like the idea of auto-creating bugs. I think that if we do this we > should make sure to set a time period after which we will evaluate whether > it has succeeded, i.e. whether bugs filed as a result of thi

Re: [PROPOSAL] Prepare Beam 2.6.0 release

should > be addressed for the release? > > Thanks, > Thomas > > > On Fri, Jul 13, 2018 at 11:02 AM Ahmet Altay wrote: > >> >> >> On Fri, Jul 13, 2018 at 10:48 AM, Pablo Estrada >> wrote: >> >>> Hi all, >>> I've triage

Re: Design Proposal for python wheels build process

Thank you Boyuan. This proposal looks good to me. I agree that it would be great to agree on this before the start of the next release. The reason is we built wheel files for the past 2 releases however we do not yet have a working process. Releases are slowed down because of that. If we can addre

Re: [PROPOSAL] Prepare Beam 2.6.0 release

at 11:19 AM, Pablo Estrada wrote: > Checking once more: > What does the communitythink we should do about https://issues.apache. > org/jira/browse/BEAM-4750 ? Should I bump it to 2.7.0? > Best > -P. > > On Fri, Jul 13, 2018 at 5:15 PM Ahmet Altay wrote: > >> Upda

Re: off for 2 - 3 weeks

Have fun! On Thu, Jul 19, 2018 at 8:46 AM, Łukasz Gajowy wrote: > Enjoy! :) > > czw., 19 lip 2018 o 16:36 Reuven Lax napisał(a): > >> Enjoy! >> >> Reuven >> >> On Thu, Jul 19, 2018 at 6:34 AM Etienne Chauchot >> wrote: >> >>> Hi all, >>> >>> Just a quick update to tell that I'll be off for 2 o

Re: Beam Docs Contributor

Welcome Rose! Looking forward to your contributions. On Fri, Jul 27, 2018 at 4:08 PM, Rose Nguyen wrote: > Hi all: > > I'm Rose! I've worked on Cloud Dataflow documentation and now I'm starting > a project to refresh the Beam docs and improve the onboarding experience. > We're planning on splitt

Re: Community Examples Repository

Thank you for this initiative. How about keeping a set of core examples in the main repository as a way of 1) convenient testing at a PR level 2) Testing with end to end tests against Beam head rather than a released Beam version 3) I think there is some educational value in having wordcount as a

Re: Community Examples Repository

Robert, I agree with you in general. However there is also a second motivation. There is an increase in new PRs that are coming to add new examples. This is great however the core code (including distributions) is not a great place to host such examples. An examples repo would help in this case. It

Re: Removing documentation for old Beam versions

I would guess that users are still using some of these old releases. It is unclear from Beam website which releases are still supported or not. It probably makes sense to drop documentation for releases < 2.0. (I would suggest keeping docs for 2.0). For the future I can work on updating the Beam we

Re: Apache Beam Python Wheels Repository

This LGTM, also greatly simplifies the creation of wheel files for multiple platforms. I can file an INFRA ticket to create a new repo to host wheel setup. Does anybody have experience with setting up a new repo similar to this? Ahmet On Fri, Aug 3, 2018 at 1:16 PM, Boyuan Zhang wrote: > Hey a

Re: Hello Beam Community!!!

Welcome! Looking forward to your contributions. On Fri, Aug 3, 2018 at 7:39 PM, Connell O'Callaghan wrote: > Hi All > > My name is Connell. I am relatively new to Beam (and Google where I work > as a technical PM). My philosophy is very much oriented around how can I > serve the team. Hence, I a

Re: [VOTE] Apache Beam, version 2.6.0, release candidate #2

+1 (binding) Thank you. On Mon, Aug 6, 2018 at 4:21 PM, Boyuan Zhang wrote: > +1 non-binding > Verified dataflow items listed in https://s.apache.org/beam- > release-validation > > On Sun, Aug 5, 2018 at 6:37 AM Suneel Marthi wrote: > >> +1 non-binding >> >> 1. verified Sigs and Hashes of arti

Re: [VOTE] Community Examples Repository

2 - Similar to Huygaa, I see value in keeping a core set of examples tested and maintained against head. At the same time I understand the value of a growing set of community grown examples that are targeted against a pre-defined versions of Beam and not necessarily updated at every release. On We

Re: [VOTE] Community Examples Repository

gt;>> >>>>> 3 - We benefit from increased test coverage by having examples >>>>> together with the rest of the code. As Robert mentions in the doc, >>>>> hosting >>>>> the Beam examples in the main repository is the best way to keep

[Discussion] Clarify the support story for released Beam versions

Hi all, I would like us to clarify the life cycle of Beam releases a little bit more for our users. I think we increased the predictability significantly by agreeing to a release cadence and kudos to everyone on that. As a follow up to that I would like to address the following problem: It is unc

Re: [DISCUSS] Communicating in dev@

Great thoughts. On Thu, Aug 9, 2018 at 9:11 AM, Rafael Fernandez wrote: > Hi, > > I think it's important we all discuss in the community what we want to > do to make sure we communicate effectively. I ask because I've seen > preferences expressed in dev@, and want to make sure we're conscious >

Re: [VOTE] Community Examples Repository

;already. Our quickstart guide for Apache Beam for the Java SDK >> >>already covers generating the examples archetype. >> >>We could point users to the starter project at the end of the >> >>java quickstart. >> >> >&

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

+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 want to create a new apache repo like beam-site >

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

h 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 clarify the life cycle of Beam releases a li

Re: Rename Nexmark jobs to Perf instead of PostCommit

+1 to rename. I agree with Andrew, flakiness and reliability problems with performance are important problems that needs to be fixed. Do we have a sense of what is making them less reliable? On Mon, Aug 13, 2018 at 10:19 AM, Jean-Baptiste Onofré wrote: > +1 > > I think it makes sense to rename.

Re: Rename Nexmark jobs to Perf instead of PostCommit

I replied before seeing Reuven's comment. In that case it makes sense to keep them as post commit tests. Are these test flaky because they fail some performance metrics? If that is the case it makes sense to separate them from functional tests. On Mon, Aug 13, 2018 at 10:30 AM, Reuven Lax wrote:

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

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 that your proposing but am wondering what value if any >>> do sup

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

hat any validations that could >> possibly be done should already be incorporated into each release? >> >> On Mon, Aug 13, 2018 at 10:57 AM Ahmet Altay wrote: >> >>> Update: >>> >>> I sent out an email to user@ to collect their feedback [1]. I will

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

of what we commit to > service. > > On Mon, Aug 13, 2018 at 12:31 PM Ahmet Altay wrote: > >> I was not proposing any additional changes to the release process. If we >> think that release process could be improved it would make sense to apply >> it to all releases. &

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

, Ahmet Altay wrote: > Still waiting for any additional user feedback to come. I added reviewers > to the PR. Unless there is objections or additional feedback I would like > to go ahead with this version as it is. Modifications after that would > always be welcome. > > On Mon, Aug 1

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

for looking into this. I have a follow-up question. Have you > thought about the next few releases, and which one will be the first LTS > release? Also, how should we track this? > -P. > > On Wed, Aug 15, 2018 at 11:24 AM Ahmet Altay wrote: > >> PR is reviewed and merged.

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

gt; next one) as LTS release by default despite of the its number in release >> sequence? >> >> On 15 Aug 2018, at 20:36, Pablo Estrada wrote: >> >> No, I think that sounds good : ) >> >> On Wed, Aug 15, 2018 at 11:34 AM Ahmet Altay wrote: >> >>&g

Re: Build failed in Jenkins: beam_PostCommit_Python_Verify #908

ValidatesRunner tests are failing, opened the https://issues.apache.org/jira/browse/BEAM-1204 issue. Root cause seems to be this commit: https://github.com/apache/incubator-beam/commit/35e2fdc7f22f20d74a569e86ced931209661dec1 On Wed, Dec 21, 2016 at 7:02 PM, Apache Jenkins Server < jenk...@builds

[DISCUSS] Python SDK status and next steps

Hi all, tl;dr: I would like to start a discussion about merging python-sdk branch to master branch. Python SDK is mature enough and merging it to master will accelerate its development and adoption. With a great effort from a lot of contributors(*), Python SDK [1] is now a mostly complete, tested

Re: [DISCUSS] Python SDK status and next steps

Thank you all for the comments so far. I would follow the process as suggested by Davor and others in this thread. Ahmet On Tue, Jan 17, 2017 at 11:47 PM, Sergio Fernández wrote: > Hi > > On Tue, Jan 17, 2017 at 5:22 PM, Ahmet Altay > wrote: > > > > tl;dr: I would li

Re: [DISCUSS] Python SDK status and next steps

ially new users/contributors that would arrive > once in master. > > [1] https://lists.apache.org/thread.html/CAAzyFAxcmexUQnbF=Y > k0plmm3f5e5bqwjz4+c5doruclnxo...@mail.gmail.com > > On Wed, Jan 18, 2017 at 12:24 AM, Ahmet Altay > wrote: > > > Thank you all for the c

[VOTE] Merge Python SDK to the master branch

Hi all, Please review the earlier discussion on the status of the Python SDK [1] and vote on merging the python-sdk branch to the master branch, as follows: [ ] +1, Merge python-sdk branch to master after the 0.5.0 release, and release it in the subsequent minor release. [ ] -1, Continue develo

Re: Build failed in Jenkins: beam_PostCommit_Python_Verify #1058

Opened: https://issues.apache.org/jira/browse/BEAM-1293 I am looking at it, it is caused by: https://github.com/apache/beam/pull/1802 On Fri, Jan 20, 2017 at 6:56 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See Verify/1

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

io Fernández > > > wrote: > > > > > > > +1 > > > > > > > > On Fri, Jan 20, 2017 at 9:24 PM, Robert Bradshaw < > > > > rober...@google.com.invalid> wrote: > > > > > > > > > On Fri, Jan 20

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

; > > > > > >* Stas Levin > > > >Stas has contributed across the breadth of the project, from the Spark > > > >runner to the core pieces and Java SDK. Looking at code contributions > > > >alone, he authored 43 commits and reported 25 issues. Stas is ve

Re: Build failed in Jenkins: beam_PostCommit_Python_Verify #1111

4 tests failed due to quota errors with project resources. I do not see any more quota errors on the project, this should fix itself in the next run. Ahmet On Sun, Jan 29, 2017 at 1:12 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See

<    3   4   5   6   7   8   9   10   >