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

Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/03/11 10:31:00 UTC

[jira] [Updated] (FLINK-16540) Fully specify bugfix version of Docker containers in Flink Playground docker-compose.yaml files

     [ https://issues.apache.org/jira/browse/FLINK-16540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated FLINK-16540:
-----------------------------------
    Labels: pull-request-available  (was: )

> Fully specify bugfix version of Docker containers in Flink Playground docker-compose.yaml files
> -----------------------------------------------------------------------------------------------
>
>                 Key: FLINK-16540
>                 URL: https://issues.apache.org/jira/browse/FLINK-16540
>             Project: Flink
>          Issue Type: Improvement
>            Reporter: Fabian Hueske
>            Assignee: Fabian Hueske
>            Priority: Major
>              Labels: pull-request-available
>
> I recently noticed that we do not guarantee client-jobmanager compatibility among different bugfix versions of the same minor version (see https://github.com/ververica/sql-training/issues/8 for details).
> In this case, a job submitted via a Flink 1.9.0 client could not be executed on a Flink 1.9.2 cluster.
> For the playgrounds this can easily happen, because we build a custom Docker image (with a fixed bugfix version) and load the latest Flink images for the latest bugfix version of the same minor version.
> We can avoid such problems by fixing the bugfix version of the Flink images that we run in the playground.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)