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

Daniel Harper commented on BEAM-5419:
-------------------------------------

Additionally AWS have recently released a new managed flink product [1] that's 
running 1.6.

I'd be eager to try running a job that's using the BEAM API (theoretically it 
should work?) but we need the flink runner to support 1.6 first. 



[1] https://aws.amazon.com/kinesis/data-analytics/ 

> 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: 2h 40m
>  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)

Reply via email to