Re: Add to Beam contributor list

What's you Jira ID ? On Fri, Mar 19, 2021 at 9:05 PM Isidro Martinez < isidro.marti...@wizeline.com> wrote: > I want to be added as a contributor to Beam Jira please. > > On Fri, Mar 19, 2021 at 6:26 PM Valentyn Tymofieiev > wrote: > >> oh, perhaps you are asking to be added as a contributor to

BEAM-9613 - BigQueryUtils and Avro

I'm working on fixing BEAM-9613 because encountered this issue as a result of using BigQueryIO.readTableRowsWithSchema() 1. BEAM-7526 provided support for Lists and Maps that came from the JSON export format 2. BEAM-2879 switched the export format from JSON to Avro. This caused issue

Re: Missing copyright notices due to LICENSE change

For visibility: Change is cherry picked to 2.29.0 release branch ( https://github.com/apache/beam/pull/14304). On Mon, Mar 22, 2021 at 12:37 PM Kenneth Knowles wrote: > So if I understand correctly, the options for a correct license in the > released artifacts are: > > - revert the change > -

BEAM-3304 - Go trigger question

Hello Team, We are trying to test the following behavior by replacing the *default* trigger in WindowingStrategy: https://github.com/apache/beam/blob/3b2b07d251f58ec00a0056ac368b443fea2f10d9/sdks/go/pkg/beam/core/runtime/graphx/translate.go Before: ws := { WindowFn: windowFn, MergeStatus:

Flaky test issue report

This is your daily summary of Beam's current flaky tests. These are P1 issues because they have a major negative impact on the community and make it hard to determine the quality of the software. BEAM-12020: :sdks:java:container:java8:docker failing missing licenses

P1 issues report

This is your daily summary of Beam's current P1 issues, not including flaky tests. See https://beam.apache.org/contribute/jira-priorities/#p1-critical for the meaning and expectations around P1 issues. BEAM-12021: PubsubReadIT failures: "Cannot nackAll on persisting checkpoint"

Re: Tutorial - How to run a Beam pipeline with Flink on Kubernetes Natively

Thanks, that looks quite useful. A not on POJOs, Serializable has several disadvantages (e.g. non-deterministic coding for key grouping, less efficient serialization). You could look into making them compatible with Beam schemas. On Mon, Mar 22, 2021 at 1:11 PM Cristian Constantinescu wrote: >

Tutorial - How to run a Beam pipeline with Flink on Kubernetes Natively

Hi everyone, I spent the week-end putting the pieces together to run Beam with the Flink Runner on Kubernetes. While I did find very good articles and videos about Beam and Flink and Kubernetes separately, I didn't find one that mixes all three of them in the same pot. So, I wrote a small demo

Re: BEAM-3415 JUnit5 support

Hi Emils, Thanks for your contribution. Luke is on vacation till June. I'm adding some java folks into your PR, who might be able to help review your PR as well. On Mon, Mar 22, 2021 at 9:17 AM Emils Solmanis wrote: > Hi all, > > The JUnit5 (BEAM-3415

Re: Missing copyright notices due to LICENSE change

So if I understand correctly, the options for a correct license in the released artifacts are: - revert the change - build some automation for bundled jars - do something manual? Kenn On Mon, Mar 22, 2021 at 10:57 AM Brian Hulette wrote: > Pros/cons for a cherrypick: > (+) Fixes regression

[Proposal] Support State Batching and Prefetching over FnApi

Hi Community, Andrew Crites and I drafted a document to discuss how to support state prefetching and batching over FnApi, which seems a missing functionality in FnApi. This will help us support Java state readLater() Api over FnApi. Please see:

Re: P0 (outage) report

Indeed. Should be done. On Mon, Mar 22, 2021 at 8:08 AM Brian Hulette wrote: > Can/should we configure this to not send the message when there are no P0s? > > On Sat, Mar 20, 2021 at 3:53 PM Beam Jira Bot wrote: > >> This is your daily summary of Beam's current outages. See >>

Re: Missing copyright notices due to LICENSE change

On Mon, Mar 22, 2021 at 10:31 AM Kenneth Knowles wrote: > Is there a Jira marked as blocking 2.29.0 for the cherrypick? > I do not think so. I have not filed a jira or started a cherry pick pr. Sorry, I was not sure if we agreed to cherry pick or not. Do you want me to do that? > > On Fri,

Re: NanosInstant not being recognised by BigQueryIO.Write

Here's https://issues.apache.org/jira/browse/BEAM-7064 on this topic. Kenn On Thu, Aug 6, 2020 at 2:27 PM Chamikara Jayalath wrote: > Created https://issues.apache.org/jira/browse/BEAM-10655 > Please add any additional information there. > > If you hope to provide a fix that's welcome too.

Re: Missing copyright notices due to LICENSE change

Is there a Jira marked as blocking 2.29.0 for the cherrypick? On Fri, Mar 19, 2021 at 6:16 PM Valentyn Tymofieiev wrote: > I also noticed (with a help of an automated tool) that > https://github.com/apache/beam/blob/master/runners/google-cloud-dataflow-java/worker/src/main/resources/NOTICES >

Re: Contributor permission for Beam Jira tickets

Done. Welcome. On Mon, Mar 22, 2021 at 9:12 AM Vitaly Terentyev < vitaly.terent...@akvelon.com> wrote: > Hello, looks like I haven't received a reply letter. > Here is my Jira username: R3tto. > > Best regards, > > Vitaly > > From: Vitaly Terentyev >

BEAM-3415 JUnit5 support

Hi all, The JUnit5 (BEAM-3415 ) has been open for quite some time, and it's been of interest to me and our organisation as well, since Beam is the only thing keeping JUnit4 around for us I took a stab at it and made a PR (#14272

RE: Contributor permission for Beam Jira tickets

Hello, looks like I haven't received a reply letter. Here is my Jira username: R3tto. Best regards, Vitaly From: Vitaly Terentyev Sent: Tuesday, 16 March 2021 11:54 To: dev@beam.apache.org Subject: Contributor permission for Beam Jira tickets This is

Re: P0 (outage) report

Can/should we configure this to not send the message when there are no P0s? On Sat, Mar 20, 2021 at 3:53 PM Beam Jira Bot wrote: > This is your daily summary of Beam's current outages. See > https://beam.apache.org/contribute/jira-priorities/#p0-outage for the > meaning and expectations around

Re: Upgrading vendored gRPC from 1.26.0 to 1.36.0

Thank you for the voting and I see the artifact available in Maven Central. I'll work on the PR to use the published artifact today. https://search.maven.org/artifact/org.apache.beam/beam-vendor-grpc-1_36_0/0.1/jar On Tue, Mar 16, 2021 at 3:07 PM Kenneth Knowles wrote: > Update on this: there

Beam Dependency Check Report (2021-03-22)

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 chromedriver-binary 88.0.4324.96.0