You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Aljoscha Krettek (Jira)" <ji...@apache.org> on 2020/04/02 08:15:00 UTC

[jira] [Closed] (FLINK-16560) Forward Configuration in PackagedProgramUtils#getPipelineFromProgram

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

Aljoscha Krettek closed FLINK-16560.
------------------------------------
    Resolution: Fixed

master: a24734ea339872763306b44770678c4ace6a369f
release-1.10: bf3c84370748e444257b49c6cdd52663f7379436

> Forward Configuration in PackagedProgramUtils#getPipelineFromProgram
> --------------------------------------------------------------------
>
>                 Key: FLINK-16560
>                 URL: https://issues.apache.org/jira/browse/FLINK-16560
>             Project: Flink
>          Issue Type: Bug
>          Components: API / DataStream, Runtime / Configuration
>    Affects Versions: 1.10.0
>            Reporter: Zhu Zhu
>            Assignee: Aljoscha Krettek
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 1.10.1, 1.11.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> PackagedProgramUtils#createJobGraph(...) is used to generate JobGraph in k8s job mode.
> The problem is that the configuration field of StreamExecutionEnvironment is a newly created one when building the job program. This is because StreamPlanEnvironment ctor will base on the no param version ctor of StreamExecutionEnvironment.
> This may lead to an unexpected result when invoking StreamExecutionEnvironment#configure(...) which relies on the configuration. Many configurations in the flink conf file will not be respected, like pipeline.time-characteristic, pipeline.operator-chaining, execution.buffer-timeout, and state backend configs.



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