cdc

Describe the bug(Please use English)
A clear and concise description of what the bug is.

Environment :

• Flink version : 1.13.1
• Flink CDC version: 2.2.1
• Database and version: 8.0.28

To Reproduce
Steps to reproduce the behavior:
mysql数据库编码为utf-8，A库的a1表的aa1字段的编码为ucs2，然后使用flink cdc读取数据，存量数据读取是乱码的；
读取binlog的新增数据是不乱码的；
然后我查了下读取binlog对aa1字段使用的utf-16编码，使用的也是utf-16解码；
读取

Hi and thank you for this great API.

Please made a Postman collection for version 3.

For example, given a simple pipeline such as:

Pipeline p = Pipeline.create();
p.readFrom(TestSources.items("the", "quick", "brown", "fox"))
 .aggregate(aggregator)
 .writeTo(Sinks.logger());

I'd like aggregator to be something requiring a non-serialisable dependency to do its work.

I know I can do this:

Pipeline p = Pipeline.create();
p.readFrom(TestSource

Fix typos in the code repository.

The flink-tidb-connector doesn't work as expected when I use upsert mode to sink data to TiDB, the reason for this is as in title, flink version: 1.13.x. Is there any reason for making unique key as part of the primary?

Code block:

private String[] getKeyFields(Context context, ReadableConfig config, String databaseName,
      String tableName) {
    // check write mode
    TiDBWr

-Dpact.rootDir="target/pact-classes" didn’t work for me.
env "pact.rootDir=target/pact-classes" bash did

...because of the "."