You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Maximilian Michels (JIRA)" <ji...@apache.org> on 2018/12/14 11:00:00 UTC

[jira] [Comment Edited] (BEAM-5419) Build multiple versions of the Flink Runner against different Flink versions

    [ https://issues.apache.org/jira/browse/BEAM-5419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721244#comment-16721244 ] 

Maximilian Michels edited comment on BEAM-5419 at 12/14/18 10:59 AM:
---------------------------------------------------------------------

The error message implies that the jar has not been correctly added to the compile path. Or the jar does not contain the FlinkRunner classes, but I've just checked on my machine that it contains all the required classes.


was (Author: mxm):
The error message implies that the jar has not been correctly added to the compile path. Or the jar does not contain the FlinkRunner classes, but I've just checked on my machine that this is the case.

> 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)