DanielLeens commented on issue #9430: URL: https://github.com/apache/seatunnel/issues/9430#issuecomment-5410158189
Thanks for following up. This thread was closed because the original reporter later confirmed the observed classpath came from a local jar/layout problem, not from a confirmed SeaTunnel core bug. On current `dev`, Oracle-CDC, TiDB-CDC, and MongoDB-CDC are still mapped to separate connector directories in `plugin-mapping.properties`, so a fresh 2.3.13 reproduction needs more installation evidence before we can tell whether this is the same problem or a different packaging/classloader issue. Could you please open a new issue in English, or update this thread in English, with the following details? 1. the exact 2.3.13 distribution and how you installed the connector (`bin/install-plugin.sh` vs manual jar copy); 2. the relevant `connectors/plugin-mapping.properties` entries; 3. the directory layout under `connectors/` and any extra JDBC jars placed under `lib/`; 4. the full stack trace from the failing run; 5. whether it still reproduces with only Oracle-CDC installed and no unrelated CDC connectors or manually copied JDBC jars present. Once those details are available, maintainers can verify whether this is a new plugin-isolation bug and route it correctly. For now, I do not want to reopen this closed thread without a fresh reproducible report because the original closure reason was different. -- 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]
