Re: [Discuss] Ideas for Apache Beam presence in social media

Bringing the PMC's conclusion back to this list, we are happy to start with the following arrangement: - Doc/spreadsheet/etc readable by dev@ (aka the public), writable by some group of contributors to set up a queue of news - Any member of PMC approves and executes the posts, with enough time

Re: Removing shading by default within BeamModulePlugin.groovy

Nice! This is a huge step. One thing that showed up in the last big gradle change was needing to check the generated poms. Kenn On Tue, Jun 4, 2019 at 5:07 PM Lukasz Cwik wrote: > Since we have been migrating to using vendoring instead of shading[1] and > due to previous efforts in

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

Final few things remaining for the release * Please review https://github.com/apache/beam/pull/8667 After which we can * Release version finalized in JIRA (PMC help needed) * Release version is listed at reporter.apache.org (PMC help needed) * Promote the release. On Tue, Jun 4, 2019 at 5:02 PM

Removing shading by default within BeamModulePlugin.groovy

Since we have been migrating to using vendoring instead of shading[1] and due to previous efforts in vendoring[2, 3] I have opened up PR 8762[4] which migrates all projects that weren't doing anything shading wise to not perform any shading. This required me to fix up all intra project

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

I would suggest have a single way of tracking cherry pick request to an RC. Currently we use emails on the RC thread, open PRs, and Jiras tagged for the release. This is confusing the person doing the release while they are juggling multiple things. How about we ask all cherry pick requests to

Re: [DISCUSS] Portability representation of schemas

Yeah that's what I meant. It does seem logical reasonable to scope any registry by pipeline and not by PCollection. Then it seems we would want the entire LogicalType (including the `FieldType representation` field) as the value type, and not just LogicalTypeConversion. Otherwise we're separating

Re: [DISCUSS] Portability representation of schemas

On Tue, Jun 4, 2019 at 9:20 AM Brian Hulette wrote: > > > On Mon, Jun 3, 2019 at 10:04 PM Reuven Lax wrote: > >> >> >> On Mon, Jun 3, 2019 at 12:27 PM Brian Hulette >> wrote: >> >>> > It has to go into the proto somewhere (since that's the only way the >>> SDK can get it), but I'm not sure

Re: Join the Beam Community Request Email

Some of the pain of switching to Hugo may be alleviated by the `hugo import jekyll` command: https://gohugo.io/commands/hugo_import_jekyll/ I guess that will probably just take care of the markdown flavor, but at least that's one less thing to worry about. Brian On Mon, Jun 3, 2019 at 11:08 PM

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

That makes sense. I would also like to add that the corresponding PR should be added to an open blocking Jira for the release to keep a single source to check. On Tue, Jun 4, 2019 at 12:15 PM Kenneth Knowles wrote: > I would

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

I would actually suggest that the following search needs to be triaged to zero before cutting an RC: https://github.com/apache/beam/pulls?utf8=%E2%9C%93=is%3Apr+is%3Aopen+base%3Arelease-2.13.0 . On Tue, Jun 4, 2019 at 11:17 AM Ankur Goenka wrote: > Sorry, I missed the comment for not including

Re: Jira tracker permission

Welcome! On Tue, Jun 4, 2019 at 9:03 AM Ahmet Altay wrote: > Welcome! > > On Mon, Jun 3, 2019 at 10:31 PM Pablo Estrada wrote: > >> I've added you as contributor - welcome >> -P. >> >> On Mon, Jun 3, 2019, 9:16 PM Yichi Zhang wrote: >> >>> Hi, beam-dev, >>> >>> This is Yichi Zhang from

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

Sorry, I missed the comment for not including weekend's to 72 hours voting period. I meant to update the blog post https://github.com/apache/beam/pull/8667/files once we have finalized the RC so that it can be consistent. Please add any comments to PR and I can incorporate them. As we did not go

Re: [DISCUSS] Portability representation of schemas

On Mon, Jun 3, 2019 at 10:04 PM Reuven Lax wrote: > > > On Mon, Jun 3, 2019 at 12:27 PM Brian Hulette wrote: > >> > It has to go into the proto somewhere (since that's the only way the >> SDK can get it), but I'm not sure they should be considered integral parts >> of the type. >> Are you just

Re: Jira tracker permission

Welcome! On Mon, Jun 3, 2019 at 10:31 PM Pablo Estrada wrote: > I've added you as contributor - welcome > -P. > > On Mon, Jun 3, 2019, 9:16 PM Yichi Zhang wrote: > >> Hi, beam-dev, >> >> This is Yichi Zhang from Google, I just started looking into beam >> projects and will be actively working

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

This seems a rushed and things fall through the cracks. Max had requested to not include the weekend into the voting period. Valentyn: I had the same question on the first RC. The PR should be included into the vote for review. You can find it here: https://github.com/apache/beam/pull/8667/files

Re: [PROPOSAL] Standardize Gradle structure in Python SDK

On Mon, Jun 3, 2019 at 5:13 PM Valentyn Tymofieiev wrote: > Hey Mark & others, > > We've been following the structure proposed in this thread to extend test > coverage for Beam Python SDK on Python 3.5, 3.6, 3.7 interpreters, see [1]. > > This structure allowed us to add 3.x suites without

Re: BQ IT tests fail on TestDataflowRunner - Python SDK

I didn't have any other changes. I ran the tests with a clean virtualenv as you suggested and it works now. :) Thanks Ahmet and Chamikara! On Tue, Jun 4, 2019 at 6:36 AM Chamikara Jayalath wrote: > Sounds like your input job was somehow incompatible with the Dataflow > worker. Running using a

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

The summary is not correct. Binding votes (in order): Ahmet Altay Robert Bradshaw Maximilian Michels Jean-Baptiste Onofré Lukasz Cwik A total of 5 binding votes. On 04.06.19 02:37, Ankur Goenka wrote: +1 Thanks for validating the release and voting. With 0(-1), 6(+1) and 3(+1 binding) votes,

Re: Timer support in Flink

One issue with the fully expanded version is that it's so large it's hard to read. I think it would be useful to make the ~ entries (at least) clickable or with hover tool tips. It would be nice to be able to expand columns individually as well. On Tue, Jun 4, 2019 at 7:20 AM Melissa Pashniak

Re: Join the Beam Community Request Email

We currently use Jekyll to generate our HTML files, and there are some plugins and hacks to add multilingual support, but it's not built-in. as I understand it, It's one of the reasons Kubernetes moved away from Jekyll to Hugo about a year ago (see their blog post for more details [1] ). They