DanielLeens commented on issue #11115: URL: https://github.com/apache/seatunnel/issues/11115#issuecomment-4729339078
Thanks for the detailed reproduction and stack trace. I traced this against the current source layout, and this does look like a real compatibility bug rather than a usage/config issue. The key problem is that the main build and Spark translation path are still aligned to Scala 2.12, but `seatunnel-scala-compiler` is pinned separately to Scala 2.13.11, and the dynamic Scala compile path initializes the REPL directly on the runtime classpath. In a Spark 2.12 runtime, that can still surface 2.13 Scala signature metadata into Spark's reflection path, which matches the `expected: 5.0 / found: 5.2` failure you hit here. So this issue is worth tracking as a bug. I also do not see this corrected yet in the current `dev` tree. As a temporary workaround, if you need to move forward before a fix lands, the practical options are: 1. avoid the SQL transform on the Spark engine for this Scala 2.12 deployment path 2. or verify with a local build where the Scala compiler side is aligned with the Spark Scala line We've also labeled this as `help wanted` so it is visible for community contribution. A PR is very welcome if someone wants to help push the fix through. -- 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]
