-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] flink1.14 ,scala-2.11 java.lang.NoSuchMethodError: scala.Predef$.refArrayOps #3680
Comments
Hello @chenhaipeng, this issue is about web, so I assign it to @Zzm0809. If you have any questions, you can comment and reply. 你好 @chenhaipeng, 这个 issue 是关于 web 的,所以我把它分配给了 @Zzm0809。如有任何问题,可以评论回复。 |
不是一个web的bug, scala的兼容问题,我不知道如何解决,我已经在所有地方指定scala的版本 |
非 dinky 问题, scala 兼容性问题 , 可添加 scala-library 另: scala-1.11 将在 dinky-v1.1.0 中移除 |
意思是要添加scal scala-library-2.11.12.jar吗,还是把jar 添加到pom里面,我测试的版本是v1.0.3 基于源码自己编译的 |
在lib 目录增加scala-library-2.11.12.jar 解决,话说pom 里面是不是需要添加 才对
|
放在部署 lib 下 或者 extends 下即可 |
只有 scala-1.11 才有可能出现此问题, 在 dinky-v1.1.0 发布后不再支持切换 scala 版本, 默认只有 scala-2.12 |
scala-2.11 也有 |
不太明白你意思,官方发布包基于scala-2.12,目前不会有此问题。无法复现。 |
|
scala-2.12 的 dinky 往 scala-2.11 的flink 提交应该可以兼容,试试看 |
我重新用dinky 1.1.0, 修改里面pom scala 版本,已经测试可以了 |
Search before asking
What happened
version info
jdk1.8 ,flink1.14 ,scala-2.11 , dinky1.0.3
when i use command compiled package ,
mvn clean package -U -DskipTests=true -P prod,flink-single-version,scala-2.11,aliyun,flink-1.14,web
i got
dinky-release-1.14-1.0.3.tgz
, but i doesn't work well and there is the following errorWhat you expected to happen
At first, I suspected it was an issue with my Scala compilation. I have already changed all the Scala versions in the pom file to 2.11, but the problem still persists.
How to reproduce
mvn clean package -U -DskipTests=true -P prod,flink-single-version,scala-2.11,aliyun,flink-1.14,web
flink-table_2.11-1.4.2.jar
flink-scala_2.11-1.14.6.jar
flink-table-runtime_2.11-1.14.6.jar
flink-table-planner_2.11-1.14.6.jar
Anything else
No response
Version
1.0.2
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: