lizhimins opened a new issue, #140: URL: https://github.com/apache/rocketmq-flink/issues/140
The connector is built against rocketmq-client 5.1.1 and rocketmq-client-java 5.2.1, several releases behind the current community versions. Two shading defects also make the SQL fat jars unusable or undiagnosable: 1. The shade `artifactSet` does not match the `relocations`. A relocation rewrites references but does not move classes into the jar, so every reference rewritten to a shaded name whose artifact was not bundled is a guaranteed `ClassNotFoundException` at runtime. 2. Both fat jars relocate `org.apache.rocketmq`, which includes the logging packages. `rmq.client.logback.xml` in rocketmq-client and `rocketmq.logback.xml` in rocketmq-client-java reference their appenders by class name in plain text, and shade rewrites class files but not class names inside XML resources. In the remoting jar the job dies at startup with `ClassNotFoundException` / `IncompatibleClassException`. In the gRPC jar every appender fails to load, the root logger ends up with no appender and the client produces zero log output, so any client side problem is invisible. rocketmq-client-java is additionally already shaded upstream (`org.apache.rocketmq.shaded.ch.qos.logback`, `org.apache.rocketmq.client.java.logging`), so relocating those packages a second time breaks its configuration the same way. Also note rocketmq-acl was retired in 5.5.x: `AclClientRPCHook` and `SessionCredentials` now ship inside rocketmq-client under the same package. RocketMQ replaced fastjson with fastjson2 as well. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
