Re: [VOTE] Release flink-connector-mongodb, release candidate #1

2023-03-31 Thread Danny Cranmer
Thanks Chesnay, This vote is now closed, I will announce the result in a separate thread. On Fri, Mar 31, 2023 at 10:46 AM Chesnay Schepler wrote: > From my side the vote can proceed. > > It's just a test problem, and we may amend the documentation a bit, but > nothing that blocks the release

Re: [VOTE] Release flink-connector-mongodb, release candidate #1

2023-03-31 Thread Chesnay Schepler
From my side the vote can proceed. It's just a test problem, and we may amend the documentation a bit, but nothing that blocks the release. On 30/03/2023 18:05, Danny Cranmer wrote: Apologies reopening the thread until we get confirmation that the test run is not a problem with the connector

Re: [VOTE] Release flink-connector-mongodb, release candidate #1

2023-03-30 Thread Danny Cranmer
Apologies reopening the thread until we get confirmation that the test run is not a problem with the connector On Thu, Mar 30, 2023 at 5:03 PM Danny Cranmer wrote: > This vote is now closed, I will announce the result in a separate thread. > > Thanks, > Danny > > On Thu, Mar 30, 2023 at 5:02 PM

Re: [VOTE] Release flink-connector-mongodb, release candidate #1

2023-03-30 Thread Danny Cranmer
This vote is now closed, I will announce the result in a separate thread. Thanks, Danny On Thu, Mar 30, 2023 at 5:02 PM Danny Cranmer wrote: > +1 (binding) > > - CI build rerun passed on the RC1 tag commit (on the second rerun) > - Validated hashes > - Verified signature > - Verified that no bi

Re: [VOTE] Release flink-connector-mongodb, release candidate #1

2023-03-30 Thread Danny Cranmer
+1 (binding) - CI build rerun passed on the RC1 tag commit (on the second rerun) - Validated hashes - Verified signature - Verified that no binaries exist in the source archive - Build the source with Maven - Verified licenses Thanks, Danny On Thu, Mar 30, 2023 at 3:32 PM Jiabao Sun wrote: > T

Re: [VOTE] Release flink-connector-mongodb, release candidate #1

2023-03-30 Thread Jiabao Sun
Thanks Danny, The test case fails again with stack trace: 14:24:57,709 [Source: Sequence Source -> Map -> Map -> Sink: Writer (1/1)#94] ERROR org.apache.flink.connector.mongodb.sink.writer.MongoWriter [] - Bulk Write to MongoDB failed com.mongodb.MongoBulkWriteException: Bulk write operation

Re: [VOTE] Release flink-connector-mongodb, release candidate #1

2023-03-30 Thread Danny Cranmer
I have restarted the build [1]. Thanks, Danny [1] https://github.com/apache/flink-connector-mongodb/actions/runs/4435527099 On Wed, Mar 29, 2023 at 4:33 PM Jiabao Sun wrote: > Thanks Chesnay, > > I noticed that problem before, the error message shows: > > Caused by: java.lang.RuntimeException:

Re: [VOTE] Release flink-connector-mongodb, release candidate #1

2023-03-29 Thread Jiabao Sun
Thanks Chesnay, I noticed that problem before, the error message shows: Caused by: java.lang.RuntimeException: com.github.dockerjava.api.exception.DockerClientException: Could not build image: Head "https://registry-1.docker.io/v2/library/openjdk/manifests/11": read tcp 10.1.0.149:34180->34.20

Re: [VOTE] Release flink-connector-mongodb, release candidate #1

2023-03-29 Thread Chesnay Schepler
+1 (binding), although I'd add a condition that someone has to look into recent test failures on Java 11: https://github.com/apache/flink-connector-mongodb/actions/runs/4222375371/jobs/7330805980 https://github.com/apache/flink-connector-mongodb/actions/runs/4435527099/jobs/7782784066 * checked

Re: [VOTE] Release flink-connector-mongodb, release candidate #1

2023-03-28 Thread Teoh, Hong
+1 (non-binding) * Hashes and Signatures look good * All required files on dist.apache.org * Tag is present in Github * Verified source archive does not contain any binary files * Source archive builds using maven Cheers, Hong > On 28 Mar 2023, at 12:56, Samrat Deb wrote: > > CAUTION: This e

Re: [VOTE] Release flink-connector-mongodb, release candidate #1

2023-03-28 Thread Samrat Deb
+1 (non-binding) - checked Source archive builds using maven - verified Hashes and Signatures - verified Tag is present in Github - checked dist.apache.org, required files present - verified source archive Bests, Samrat On Mon, Mar 20, 2023 at 2:08 PM Leonard Xu wrote: > > > + 1 (non-

Re: [VOTE] Release flink-connector-mongodb, release candidate #1

2023-03-23 Thread Jiabao Sun
Thanks Leonard for the suggestion. - Check that all POM files point to the same version - Build the source with Maven - Ran end-to-end tests locally and succeeded - Tested read from and write to MongoDB by local cluster. - Tested lookup table feature by local cluster. Tested read from and writ

Re: [VOTE] Release flink-connector-mongodb, release candidate #1

2023-03-20 Thread Leonard Xu
> + 1 (non-binding) > > Best, > Jiaba Hi, Jiabao Thanks for help to verify the release candidate. But we need to do the verification firstly and then post the verified items when in a release candidate vote thread. The community does not require verification of all items in the document [

Re: [VOTE] Release flink-connector-mongodb, release candidate #1

2023-03-20 Thread Jiabao Sun
Thanks Danny for driving this. + 1 (non-binding) Best, Jiabao > 2023年3月17日 上午4:32,Martijn Visser 写道: > > +1 (binding) > > - Validated hashes > - Verified signature > - Verified that no binaries exist in the source archive > - Build the source with Maven > - Verified licenses > - Verified web

Re: [VOTE] Release flink-connector-mongodb, release candidate #1

2023-03-16 Thread Martijn Visser
+1 (binding) - Validated hashes - Verified signature - Verified that no binaries exist in the source archive - Build the source with Maven - Verified licenses - Verified web PRs On Thu, Mar 16, 2023 at 11:21 AM Danny Cranmer wrote: > Hi everyone, > Please review and vote on the release candidat

[VOTE] Release flink-connector-mongodb, release candidate #1

2023-03-16 Thread Danny Cranmer
Hi everyone, Please review and vote on the release candidate # for the version , as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) The complete staging area is available for your review, which includes: * JIRA release notes [1], * the of