Re: Next LTS?

2019-09-23 Thread Lukasz Cwik
I agree with what Lukasz Gajowy mentioned. I find that Jenkins is fine when your developing at HEAD but as soon as you cut a branch, the jenkins configuration starts to drift as it keeps getting updated to HEAD with the seed job. I was always thinking that the Jenkins configurations would be as

Re: Plan for dropping python 2 support

2019-09-23 Thread Kyle Weaver
Re feedback collection, we already print a message: "You are using Apache Beam with Python 2. New releases of Apache Beam will soon support Python 3 only." When users run Python 2 pipelines. This might be a good place to provide additional info along with a place to send feedback (probably user@).

Re: Collecting feedback for Beam usage

2019-09-23 Thread Robert Bradshaw
On Mon, Sep 23, 2019 at 3:08 PM Brian Hulette wrote: > > Would people actually click on that link though? I think Kyle has a point > that in practice users would only find and click on that link when they're > having some kind of issue, especially if the link has "feedback" in it. I think the

Re: Collecting feedback for Beam usage

2019-09-23 Thread Chad Dombrova
A survey would be a good place to start. This came up in the python2-sunsetting thread as well: we don't know what versions of python people are using with Beam, which makes it difficult to answer the question of support. -chad On Mon, Sep 23, 2019 at 2:57 PM Ankur Goenka wrote: > I agree,

Re: Collecting feedback for Beam usage

2019-09-23 Thread Brian Hulette
Would people actually click on that link though? I think Kyle has a point that in practice users would only find and click on that link when they're having some kind of issue, especially if the link has "feedback" in it. I agree usage data would be really valuable, but I'm not sure that this

Re: Collecting feedback for Beam usage

2019-09-23 Thread Ankur Goenka
I agree, these are the questions that need to be answered. The data can be anonymize and stored as public data in BigQuery or some other place. The intent is to get the usage statistics so that we can get to know what people are using Flink or Spark etc and not intended for discussion or a help

Beam meetup Seattle!! September 26th, 6pm

2019-09-23 Thread Pablo Estrada
Hello everyone! If you are in the Seattle area please come to Beam meetup this Thursday, September 26th - at 6pm in the Google office in Fremont. There will be interesting talks, and there should be a number of Beam contributors and users around. Also pizza and drinks. The page with al the info:

No filesystem found for scheme s3 using FileIO.write()

2019-09-23 Thread Koprivica,Preston Blake
Hello everyone. This is a cross-post from the users list. It didn’t get much traction, so I thought I’d move over to the dev group, since this seems like it might be a an issue with initialization in the FlinkRunner (apologies in advance if I missed something silly). I’m getting the following

Re: contributor permission for Beam Jira tickets

2019-09-23 Thread dev wearebold
Awesome it works! Cheers, J > Le 23 sept. 2019 à 13:46, Ismaël Mejía a écrit : > > Can you please try again, it seems you were assigned into a different > role. It should be ok now. > > > On Sat, Sep 21, 2019 at 5:44 PM dev wearebold wrote: >> >> Hey! >> >> Unluckily I see I’m not be

Beam Dependency Check Report (2019-09-23)

2019-09-23 Thread Apache Jenkins Server
High Priority Dependency Updates Of Beam Python SDK: Dependency Name Current Version Latest Version Release Date Of the Current Used Version Release Date Of The Latest Release JIRA Issue mock 2.0.0 3.0.5 2019-05-20

Re: contributor permission for Beam Jira tickets

2019-09-23 Thread Ismaël Mejía
Can you please try again, it seems you were assigned into a different role. It should be ok now. On Sat, Sep 21, 2019 at 5:44 PM dev wearebold wrote: > > Hey! > > Unluckily I see I’m not be able to assign tickets to myself. > > Maybe it’s because I’ve created them before getting the permission?