[
https://issues.apache.org/jira/browse/BEAM-5419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721288#comment-16721288
]
Giorgos Stamatakis commented on BEAM-5419:
------------------------------------------
This is my last question since I have already asked a lot of them.
Im trying to replace in pom.xml the already existing beam-runners-flink_2.11
dependency (which works up to 1.5.5) with the new one from the compiled
sources beam-runners-flink-1.6-2.10.0-SNAPSHOT.jar. But its still undetected
when Im running the pipeline (error: cant find FlinkRunner)
> 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)
