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

ASF GitHub Bot logged work on BEAM-5419:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 08/Dec/18 00:26
            Start Date: 08/Dec/18 00:26
    Worklog Time Spent: 10m 
      Work Description: mxm commented on issue #7229: [BEAM-5419] Add Flink 
multi-version builds
URL: https://github.com/apache/beam/pull/7229#issuecomment-445411431
 
 
   Run Java PreCommit

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 173122)
    Time Spent: 1h  (was: 50m)

> 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: 1h
>  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