DanielLeens commented on issue #10832: URL: https://github.com/apache/seatunnel/issues/10832#issuecomment-5154871640
Thanks again for the original report. The misleading plugin-discovery log path discussed above is already addressed on current `dev`, so this thread now looks like a verification follow-up rather than an active implementation gap. If you have verified the latest `dev` build, or a release that includes that fix, and you no longer see the same misleading `Load SeaTunnelSink Plugin ...` behavior, please close this issue. If it still happens, please reply with: 1. the exact SeaTunnel version or commit; 2. the full parser / plugin-discovery log around `getConnectorJarList(...)`; 3. whether the problem is only the incorrect log classification, or also a real connector loading failure. That will let us continue from the current code path instead of the older already-fixed one. -- 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]
