[
https://issues.apache.org/jira/browse/BEAM-5419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giorgos Stamatakis updated BEAM-5419:
-------------------------------------
Comment: was deleted
(was: Thank you for your time but it appears that even after installing (and
including in the pom.xml) the flink-1.6 ~3MB jar an error still pops up:
java.lang.NoClassDefFoundError: org/apache/flink/streaming/api/CheckpointingMode
mvn package exec:java Dexec.mainClass=myPipeline
"Dexec.args-=--runner=FlinkRunner --flinkMaster=localhost:8081 --streaming=true
--parallelism=4 --windowSize=10 --filesToStage=target/XXX-bundled-flink.jar"
-Pflink-runner
Trying to run on a 1.6.2 cluster.The pom.xml flink profile is the following:
<profile>
<id>flink-runner</id>
<dependencies>
<dependency>
<groupId>org.apache.beam</groupId>
<artifactId>beam-runners-flink-1.6</artifactId>
<version>2.10.0</version>
<scope>runtime</scope>
</dependency>
</dependencies>
</profiles>
If there is a sample pom.xml Im interested)
> Build multiple versions of the Flink Runner against different Flink versions
> ----------------------------------------------------------------------------
>
> Key: BEAM-5419
> URL: https://issues.apache.org/jira/browse/BEAM-5419
> Project: Beam
> Issue Type: New Feature
> Components: build-system, runner-flink
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Priority: Major
> Fix For: 2.10.0
>
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> Following up on a discussion on the mailing list.
> We want to keep the Flink version stable across different versions to avoid
> upgrade pain for long-term users. At the same time, there are users out there
> with newer Flink clusters and developers also want to utilize new Flink
> features.
> It would be great to build multiple versions of the Flink Runner against
> different Flink versions.
> When the upgrade is as simple as changing the version property in the build
> script, this should be pretty straight-forward. If not, having a "base
> version" and applying a patch during the build could be an option. We should
> avoid duplicating any Runner code.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
