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 error on
server localhost:32770. Write errors: [BulkWriteError{index=0, code=11000,
message='E11000 duplicate key error collection:
test_sink.test-recovery-mongo-sink index: _id_ dup key: { : 1 }',
details={}}].
at
com.mongodb.internal.connection.BulkWriteBatchCombiner.getError(BulkWriteBatchCombiner.java:167)
~[mongodb-driver-core-4.7.2.jar:?]
at
com.mongodb.internal.connection.BulkWriteBatchCombiner.throwOnError(BulkWriteBatchCombiner.java:192)
~[mongodb-driver-core-4.7.2.jar:?]
at
com.mongodb.internal.connection.BulkWriteBatchCombiner.getResult(BulkWriteBatchCombiner.java:136)
~[mongodb-driver-core-4.7.2.jar:?]
at
com.mongodb.internal.operation.BulkWriteBatch.getResult(BulkWriteBatch.java:237)
~[mongodb-driver-core-4.7.2.jar:?]
The test case may be connected to the same test container when running
the test case at same time.
I’m looking into it.
Best,
Jiabao
2023年3月30日 下午10:05,Danny Cranmer <dannycran...@apache.org> 写道:
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 <jiabao....@xtransfer.cn
.invalid>
wrote:
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.205.13.154:443: read: connection reset
by
peer
I think that may be some network problem to download java11 docker
image.
Could you help re-run the failed cases again?
Best,
Jiabao
2023年3月29日 下午10:08,Chesnay Schepler <ches...@apache.org> 写道:
+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 source release content
* check website PR
On 28/03/2023 15:25, Teoh, Hong wrote:
+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 <decordea...@gmail.com>
wrote:
CAUTION: This email originated from outside of the organization. Do
not click links or open attachments unless you can confirm the sender
and
know the content is safe.
+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 <xbjt...@gmail.com>
wrote:
+ 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
[1], each contributor can determine the items they need to verify
based on
the modules they are familiar with and the features they care
about.
Best,
Leonard
[1]
https://cwiki.apache.org/confluence/display/FLINK/Verifying+a+Flink+Release
2023年3月17日 上午4:32,Martijn Visser <martijnvis...@apache.org> 写道:
+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 <
dannycran...@apache.org
wrote:
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 official Apache source release to be deployed to
dist.apache.org
[2],
which are signed with the key with fingerprint
0F79F2AFB2351BC29678544591F9C1EC125FD8DB [3],
* all artifacts to be deployed to the Maven Central Repository
[4],
* source code tag v1.0.0-rc1 [5],
* website pull request listing the new release [6].
Given this is a new connector I will follow-up with a blog,
but it
will not
block the release.
The vote will be open for at least 72 hours (ending 2023-03-21
11:00
UTC).
It is adopted by majority approval, with at least 3 PMC
affirmative
votes.
Thanks,
Danny
[1]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522&version=12352386
[2]
https://dist.apache.org/repos/dist/dev/flink/flink-connector-mongodb-1.0.0-rc1/
[3] https://dist.apache.org/repos/dist/release/flink/KEYS
[4]
https://repository.apache.org/content/repositories/orgapacheflink-1598
[5]
https://github.com/apache/flink-connector-mongodb/releases/tag/v1.0.0-rc1
[6] https://github.com/apache/flink-web/pull/622