feat(cdc): Add MongoDB CDC Source

[StrikeW]

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

1. Add mongodb-cdc connector to support capturing cdc events from MongoDB
2. Extend the DebeziumMongoJsonParser to handle message key, because we need to extract the _id field for DELETE event
3. Refactor cdc split implementation
4. User can use following query to ingest and capture collections in the dev database

CREATE TABLE test (
   _id varchar PRIMARY KEY,
   payload jsonb
) WITH (
   connector='mongodb-cdc',
   mongodb.url='mongodb://localhost:27017/?replicaSet=rs0',
   collection.name='dev.*'
);

Unit test and e2e tests will be added in follow up #15003

#14759

Checklist

• I have written necessary rustdoc comments
• I have added necessary unit tests and integration tests
• I have added test labels as necessary. See details.
• I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features Sqlsmith: Sql feature generation #7934).
• My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
• All checks passed in ./risedev check (or alias, ./risedev c)
• My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

• My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

• My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note

• Add mongodb-cdc connector to support capturing cdc events from MongoDB

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
9425213	Triggered	Generic Password	8433b84	ci/scripts/regress-test.sh	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>

[neverchanje]

Good job!

• I wonder if we support multiple mongodb addresses? It'd be common to have multiple mongodb nodes in real cases.
• Is FORMAT DEBEZIUM_MONGO ENCODE JSON; still needed for the new source?

[StrikeW]

Good job!

• I wonder if we support multiple mongodb addresses? It'd be common to have multiple mongodb nodes in real cases.

I think we do. The underlying debezium connector can support replica set and shared cluster deployment. User just need to provide the corresponding connection string to us:

• replica set
  mongodb://user:password@mongodb0.example.com:27017,mongodb1.example.com:27017,mongodb2.example.com:27017/?replicaSet=myRepl

• sharded cluster
  mongodb://user:password@mongos0.example.com:27017,mongos1.example.com:27017,mongos2.example.com:27017/

• Is FORMAT DEBEZIUM_MONGO ENCODE JSON; still needed for the new source?

Yeah, we can omit it from the sql.

[neverchanje]

Please forbid unnecessary attributes in the final syntax, since a direct mongodb source does not require them.

[neverchanje]

Tried my best reviewing the code. Still some code to refine, but overall LGTM. Please find engineers to approve this PR.

[fuyufjh]

Recommend parsing all possible values (mongodb-cdc, postgres-cdc, mysql-cdc) to enum and use equal conditions here. This code looks too lossy, and it's hard to say what will happen if I pass some strange values ending with -cdc.

[StrikeW]

leave to the PR that adding e2e tests.

[StrikeW]

@fuyufjh @hzxa21 @tabVersion PTAL again, I‘d like to get the basic functionality merge first.

[fuyufjh]

Any motivation for this change? In what situation will it failed with error == null?

[StrikeW]

For defensive of nullptr and match the implementation of the following create(DbzConnectorConfig config, long channelPtr) method.
Actually newCdcEngineRunner only used in unit test right now, since we replaced with embeded jvm.

[fuyufjh]

LGTM. Thanks!