Re: [DISCUSS] Migrate Jira to GitHub Issues?

Hi, No problem for me. The only thing I don’t like with GitHub issues is that fact that it’s not possible to “assign” several milestones to an issue. When we maintain several active branch/version, it sucks (one issue == one milestone), as we have to create several issue. Regards JB > Le 10

Re: Intro

Welcome ;) Regards JB > Le 22 oct. 2021 à 15:52, Moritz Mack a écrit : > > Hi all, > > I’m very much looking forward to start contributing to Beam and just want to > briefly introduce myself. > > My name is Moritz (mosche) and I’m working together with Alexey and Etienne. > Having worked

Re: [VOTE] Vendored Dependencies Release Byte Buddy 1.11.0

+1 (binding) Regards JB > Le 20 mai 2021 à 10:56, Etienne Chauchot a écrit : > > +1 (binding) on releasing vendored bytebuddy for testing in > https://github.com/apache/beam/pull/14824 > > Etienne > > On 19/05/2021 23:43, Kai Jiang wrote: >> +1

Re: LGPL-2.1 in beam-vendor-grpc

+1 fully agree. Regards JB > Le 10 mai 2021 à 16:02, Jan Lukavský a écrit : > > +1 for blocking the release - I think we should not release something about > which we _know_ that it might be legally problematic. And we should > definitely create a check in the build process that will warn

Re: Lots of branches

+1 On other projects, I have script mostly doing: $ git branch —merged $ git branch -d MERGED $ git remote prune REMOTE Regards JB > Le 8 mai 2021 à 02:35, Ahmet Altay a écrit : > > Hello all, > > Our git repo has lots of branches for cherry picks, patches, reverts etc. I > believe these

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

+1 (binding) Regards JB > Le 16 avr. 2021 à 06:01, Kenneth Knowles a écrit : > > Hi everyone, > > Please review and vote on the release candidate #1 for the version 2.29.0, as > follows: > > [ ] +1, Approve the release > [ ] -1, Do not approve the release (please provide specific comments)

Re: [DISCUSS] Drop support for Flink 1.8 and 1.9

+1 Regards JB > Le 11 mars 2021 à 19:18, Ismaël Mejía a écrit : > > Hello, > > We have been supporting older versions of Flink that we had agreed in previous > discussions where we said we will be supporting only the latest three releases > [1]. > > I would like to propose that for Beam

Re: [VOTE] Release vendor-calcite-1_26_0 version 0.1, release candidate #1

+1 (binding) Regards JB > Le 8 mars 2021 à 20:37, Andrew Pilloud a écrit : > > Hi everyone, > Please review and vote on the release candidate #1 for > beam-vendor-calcite-1_26_0 version 0.1, as follows: > [ ] +1, Approve the release > [ ] -1, Do not approve the release (please provide

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

+1 (binding) Regards JB > Le 15 févr. 2021 à 21:01, Chamikara Jayalath a écrit : > > Hi everyone, > > Please review and vote on the release candidate #1 for the version 2.28.0, as > follows: > [ ] +1, Approve the release > [ ] -1, Do not approve the release (please provide specific comments)

Re: BEAM-6516 - RabbitMqIO.Read - Caused by: com.rabbitmq.client.ShutdownSignalException: channel error; protocol method: #method(reply-code=406, reply-text=PRECONDITION_FAILED - unknow

Hi, Let me take a look. Regards JB > Le 15 janv. 2021 à 20:43, Rafael Ribeiro a écrit : > > hi All, > > I'm facing the problem reported on > https://issues.apache.org/jira/browse/BEAM-6516 > > > running a flex template based on

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

+1 (binding) Regards JB > Le 6 janv. 2021 à 08:17, Pablo Estrada a écrit : > > Hi everyone, > Please review and vote on the release candidate #4 for the version 2.27.0, as > follows: > [ ] +1, Approve the release > [ ] -1, Do not approve the release (please provide specific comments) > >

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

+1 (binding) Regards JB > Le 23 déc. 2020 à 06:46, Pablo Estrada a écrit : > > Hi everyone, > Please review and vote on the release candidate #1 for the version 2.27.0, as > follows: > [ ] +1, Approve the release > [ ] -1, Do not approve the release (please provide specific comments) > > >

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

+1 (binding) Sorry for the delay. Regards JB > Le 10 déc. 2020 à 17:40, Tyson Hamilton a écrit : > > +1 from me. I validated Nexmark performance tests. > > On Tue, Dec 8, 2020 at 7:53 PM Robert Burke > wrote: > I'm +1 on RC1 based on the 7 tests I know I can check

Re: DRAFT - Beam board report June 2020

Hi, It looks good with the latest proposed changes. Regards JB > Le 9 juin 2020 à 20:36, Kenneth Knowles a écrit : > > Ping! It is now June, and time to submit this report. Please add interesting > tidbits from the last quarter. Perhaps find highlights in >

Re: Difficulties with triggering PRs Jenkins jobs

Hi, Actually, it’s because of the PR plugin we are using on Jenkins. We have the choice between two plugins: - the "old/deprecated" one that allow key sentence like "retest this please". I’m still using it on projects like Karaf just for that ;) - the "new" plugin just trigger build when the

Re: How to build Beam locally (with just the bare minimum for Java SDK and runners)?

Hi, Personally I’m use: ./gradlew :sdks:java:build … And ./gradlew projects gives you the name of the module. Regards JB > Le 24 mai 2020 à 11:32, Jacek Laskowski a écrit : > > Hi Thomas, > > > Most of the developer documentation can be found on the cwiki, in this case > > That's the

Re: Companies using Beam?

Hi, We already have some testimonials on Beam home page (I did the one about Beam use at Talend). It makes sense to have a dedicated section as it gives ideas about use case and production system running with Beam. Regards JB > Le 28 avr. 2020 à 23:42, Austin Bennett a écrit > : > > Hi

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

+1 (binding) Quickly checked on beam-samples. Regards JB > Le 10 avr. 2020 à 17:25, Kenneth Knowles a écrit : > > +1 > > Ran a small Java pipeline. > > Noting that the version in gradle.properties is 2.20.0-RC2: > https://github.com/apache/beam/blob/v2.20.0-RC2/gradle.properties#L26 >

Re: Question about updating documents on MongoDB

Hi, Not sure I understand fully your use case, but you can add/update document with Write: pipeline .apply(...) .apply(MongoDbIO.write() .withUri("mongodb://localhost:27017") .withDatabase("my-database") .withCollection("my-collection") .withNumSplits(30)) It’s using

Re: [PROPOSAL] Snowflake Java Connector for Apache Beam

Hi, It’s very interesting. +1 to create a Jira and prepare a PR for review. Thanks ! Regards JB > Le 23 mars 2020 à 15:23, Katarzyna Kucharczyk a > écrit : > > Hi all, > > Me and my colleagues have developed a new Java connector for Snowflake that > we would like to add to Beam. > >

Re: A new reworked Elasticsearch 7+ IO module

Hi, I think WARN makes sense and the safest approach. It allows users to be notify and eventually update or back on previous Beam IO version. Regards JB > Le 6 mars 2020 à 18:49, Kenneth Knowles a écrit : > > Since the user provides backendVersion, here are some possible levels of > things

Re: [VOTE] Vendored Dependencies Release gRPC 1.26.0 v0.3 for BEAM-9288 RC #3

+1 (binding) Regards JB > Le 5 mars 2020 à 19:55, Luke Cwik a écrit : > > Please review the release of the following artifacts that we vendor: > * beam-vendor-grpc-1_26_0 > > Hi everyone, > Please review and vote on the release candidate #1 for the version 0.3, as > follows: > [ ] +1,

Re: [VOTE] Upgrade gradle to 6.2

Fair enough, we have the consensus, so agree to create Jira and move forward about this update. Regards JB > Le 5 mars 2020 à 20:16, Ismaël Mejía a écrit : > > Looks like we have consensus on this one. Can you create a JIRA to > track this Alex. > I found this interesting presentation and

Re: JdbcIO for writing to Dynamic Schemas in Postgres

Hi You have the setPrepareStatement() method where you define the target tables. However, it’s in the same database (datasource) per pipeline. You can define several datasources and use a different datasource in each JdbcIO write. Meaning that you can divide in sub pipelines. Regards JB > Le

Re: [VOTE][BIP-1] Beam Schema Options

+1 (binding) Very interesting. It remembers me when we start the discussion about schema support ;) Regards JB > Le 20 févr. 2020 à 08:36, Alex Van Boxel a écrit : > > Hi all, > > let's do a vote on the very first Beam Improvement Proposal. If you have a -1 > or -1 (binding) please add

Re: Compile error on Java 11 when running :examples:java:test

Hi, AFAIR I had the same issue on my Linux. Let me do a new run. Regards JB > Le 7 févr. 2020 à 21:35, Kenneth Knowles a écrit : > > The expected class file version 53 is for Java 9, I believe. So is the right > javac being invoked? > > I hit some issues like this on mac a while back,

Re: Transitive dependency from external repository

Like this: repositories { jcenter() maven { url "https://plugins.gradle.org/m2/; } maven { url "https://repo.spring.io/plugins-release/; content { includeGroup "io.spring.gradle" } } maven { url "foo" } } > Le 6 févr. 2020 à 18:37, Jean-Bapt

Re: Transitive dependency from external repository

uent/kafka-avro-serializer/5.4.0/kafka-avro-serializer-5.4.0.pom > > <https://packages.confluent.io/maven/io/confluent/kafka-avro-serializer/5.4.0/kafka-avro-serializer-5.4.0.pom> > >> On 6 Feb 2020, at 18:12, Jean-Baptiste Onofre > <mailto:j...@nanthrax.net>> wrote: &

Re: Transitive dependency from external repository

Hi, Just a side note: did you check the license of the dependency (just to be sure it’s not a Cat X dependency) ? Regards JB > Le 6 févr. 2020 à 18:06, Alexey Romanenko a écrit : > > Hi, > > To add support of Confluent Registry Schema in KafkaIO we added new > dependency on

Re: A new reworked Elasticsearch 7+ IO module

nd they are not as > closely observed as UTests. > > Etienne > > On 05/02/2020 11:32, Jean-Baptiste Onofre wrote: >> Hi, >> >> We talked in the past about multiple/single module. >> >> IMHO the always preferred goal is to have a single module. H

Re: A new reworked Elasticsearch 7+ IO module

Hi, We talked in the past about multiple/single module. IMHO the always preferred goal is to have a single module. However, it’s tricky when we have such difference, including on the user facing API. So, I would go with module per version, or use a specified version for a target Beam release.