You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had searched in the feature and found no similar feature requirement.
Description
Problem Description
Currently, seatunnel-connectors-v2/connector-cdc/connector-cdc-sqlserver and seatunnel-connectors-v2/connector-maxcompute is encountering dependency conflicts. Specifically, they contain classes with the same qualified class names in their dependencies as listed below.
Dep org.apache.seatunnel:connector-cdc-sqlserver:2.3.2:
Pulled in by: [org.apache.seatunnel:connector-cdc-sqlserver:2.3.2::]
Dep io.debezium:debezium-connector-sqlserver:1.6.4.Final:
Pulled in by: [org.apache.seatunnel:connector-cdc-sqlserver:2.3.2:: -> io.debezium:debezium-connector-sqlserver:1.6.4.Final::compile]
Contains Duplicate Classes: 1
io.debezium.connector.sqlserver.SqlServerStreamingChangeEventSource
----
Dep org.apache.seatunnel:connector-maxcompute:2.3.2:
Pulled in by: [org.apache.seatunnel:connector-maxcompute:2.3.2::]
Dep com.aliyun.odps:odps-sdk-commons:0.31.3-public:
Pulled in by: [org.apache.seatunnel:connector-maxcompute:2.3.2:: -> com.aliyun.odps:odps-sdk-core:0.31.3-public::compile -> com.aliyun.odps:odps-sdk-commons:0.31.3-public::compile]
Contains Duplicate Classes: 3
com.aliyun.odps.type.SimpleMapTypeInfo
com.aliyun.odps.type.SimpleStructTypeInfo
com.aliyun.odps.type.SimpleArrayTypeInfo
----
The behavior of the Java classloader indictates that when multiple classes with the same fully qualified name exist on the classpath, only one instance of the class will be loaded into memory at runtime. This means that the classes defined here may actually not be loaded, leading to runtime error or semantic conflicts, etc.
Search before asking
Description
Problem Description
Currently, seatunnel-connectors-v2/connector-cdc/connector-cdc-sqlserver and seatunnel-connectors-v2/connector-maxcompute is encountering dependency conflicts. Specifically, they contain classes with the same qualified class names in their dependencies as listed below.
The behavior of the Java classloader indictates that when multiple classes with the same fully qualified name exist on the classpath, only one instance of the class will be loaded into memory at runtime. This means that the classes defined here may actually not be loaded, leading to runtime error or semantic conflicts, etc.
Usage Scenario
No response
Related issues
No response
Are you willing to submit a PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: