[Optimization][CDCSOURCE] whole repository synchronization support kafka source multi-topic synchronization

[XIJIU123]

Search before asking

• I had searched in the issues and found no similar optimization requirement.

Description

Referring to the way of cdc whole library synchronization, the data source is one or more topics of kafka, and the data sink side is multiple tables of mysql. Data triage can be differentiated according to the content of the topic's source. Dezium-json data format example:

{
	"before": {
		"id": 1
	},
	"after": {
		"id": -4
	},
	"source": {
		"version": "xxx",
		"connector": "mysql",
		"name": "mysql_binlog_source",
		"ts_ms": xxxx,
		"snapshot": "false",
		"db": "db",
		"sequence": null,
		"table": "table_name",
		"server_id": xxx,
		"gtid": "xxx",
		"file": "xxx",
		"pos": xxx,
		"row": 0,
		"thread": null,
		"query": null
	},
	"op": "u",
	"ts_ms": xxx,
	"transaction": null
}

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[github-actions]

Hello @XIJIU123, this issue is about CDC/CDCSOURCE, so I assign it to @aiwenmo. If you have any questions, you can comment and reply.

你好 @XIJIU123, 这个 issue 是关于 CDC/CDCSOURCE 的，所以我把它分配给了 @aiwenmo。如有任何问题，可以评论回复。

[aiwenmo]

How to obtain metadata for tables?

[XIJIU123]

How to obtain metadata for tables?
Because of the whole library synchronization method, the table structure of the source and the write side should remain the same. You can use the metadata of the write side as the metadata of the source side.