selvinsource edited a comment on issue #3092: [ZEPPELIN-3653] - New Java interpreter URL: https://github.com/apache/zeppelin/pull/3092#issuecomment-468902863 > oh wait, I didn't realize this comment [#3092 (comment)](https://github.com/apache/zeppelin/pull/3092#issuecomment-410957256) is not related to ZEPPELIN-3742 > > do we need a fix for `beam-runners-flink_2.10` As I mentioned before, that's nothing new, it's been there since the Beam interpreter was added, it never supported scala 2.11, see the notes on https://github.com/apache/zeppelin/blob/master/beam/README.md "Flink runner comes with binary compiled for scala 2.10. So, currently we support only Scala 2.10". By doing a quick search somebody else already created JIRAs for this https://issues.apache.org/jira/browse/ZEPPELIN-3903 https://issues.apache.org/jira/browse/ZEPPELIN-3899 @novelari perhaps is in the best position to update the beam-runners-flink to a most up to date version to support both scala 2.10 and 2.11, I am not that familiar with Beam/Flink. A solution could be to use profiles in beam/pom.xml to activate either https://mvnrepository.com/artifact/org.apache.beam/beam-runners-flink_2.10/2.2.0 or https://mvnrepository.com/artifact/org.apache.beam/beam-runners-flink_2.11/2.3.0 depending on the scala version. For example ```xml <profiles> <profile> <id>scala-2.10</id> <activation> <activeByDefault>true</activeByDefault> </activation> <dependencies> <dependency> <groupId>org.apache.beam</groupId> <artifactId>beam-runners-flink_2.10</artifactId> <version>2.2.0</version> </dependency> </dependencies> </profile> <profile> <id>scala-2.11</id> <dependencies> <dependency> <groupId>org.apache.beam</groupId> <artifactId>beam-runners-flink_2.11</artifactId> <version>2.3.0</version> </dependency> </dependencies> </profile> </profiles> ```
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
