You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@beam.apache.org by "Ahmet Altay (JIRA)" <ji...@apache.org> on 2018/10/03 23:41:00 UTC

[jira] [Commented] (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=16637623#comment-16637623 ] 

Ahmet Altay commented on BEAM-5419:
-----------------------------------

What is the plan for this JIRA? Are we targeting 2.8.0 with cut date 10/10?

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