Flink CDC Issue Import created FLINK-34860:
----------------------------------------------

             Summary: [Bug] Jackson version conflicts among MySQL/TiDB/MongoDB 
connectors
                 Key: FLINK-34860
                 URL: https://issues.apache.org/jira/browse/FLINK-34860
             Project: Flink
          Issue Type: Bug
          Components: Flink CDC
            Reporter: Flink CDC Issue Import


### Search before asking

- [X] I searched in the 
[issues|https://github.com/ververica/flink-cdc-connectors/issues) and found 
nothing similar.


### Flink version

1.14

### Flink CDC version

3.0.0

### Database and its version

MySQL 5.7

### Minimal reproduce step

Put `flink-sql-connector-tidb-cdc-3.0.0.jar`, 
`flink-sql-connector-mysql-cdc-3.0.0.jar` and 
`flink-sql-connector-mongodb-cdc-3.0.0.jar` into lib folder at Flink home 
(Flink 1.14 in my case], then create a MySQL CDC table and submit a simple 
query like `select * from mysql_cdc_table`, there would be an error:

`java.io.InvalidClassException: 
com.ververica.cdc.connectors.shaded.com.fasterxml.jackson.databind.cfg.MapperConfig;
 incompatible types for field _mapperFeatures`

It's caused by inconsistent jackson versions of the CDC connectors:

- `flink-sql-connector-mongodb-cdc-3.0.0.jar`: 2.10.2
- `flink-sql-connector-mysql-cdc-3.0.0.jar`: 2.13.2
- `flink-sql-connector-tidb-cdc-3.0.0.jar`: 2.12.3

### What did you expect to see?

All CDC connectors use the same jackson version.

### What did you see instead?

Inconsistent jackson versions among the CDC connectors which conflicts with 
each other.

### Anything else?

_No response_

### Are you willing to submit a PR?

- [X] I'm willing to submit a PR!

---------------- Imported from GitHub ----------------
Url: https://github.com/apache/flink-cdc/issues/2983
Created by: [link3280|https://github.com/link3280]
Labels: bug, 
Assignee: [link3280|https://github.com/link3280]
Created at: Wed Jan 10 10:28:58 CST 2024
State: open




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to