[
https://issues.apache.org/jira/browse/FLINK-17586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17103262#comment-17103262
]
Dian Fu edited comment on FLINK-17586 at 5/9/20, 11:35 AM:
-----------------------------------------------------------
Merged to master via 1a734c2b95fab7b2a0b62e5aded899b1efd91508 and
61fe14f3a2ebf31891187eff1a9a6fb92b35c776
was (Author: dian.fu):
Merged to master via 1a734c2b95fab7b2a0b62e5aded899b1efd91508
> Due to the new behavior of the flink-table module the Python dependency
> management command line options does not work
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-17586
> URL: https://issues.apache.org/jira/browse/FLINK-17586
> Project: Flink
> Issue Type: Bug
> Components: API / Python
> Affects Versions: 1.11.0
> Reporter: Wei Zhong
> Assignee: Wei Zhong
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.11.0
>
>
> Currently the Python dependency management command line options does not work
> because of such changes on flink-table module:
> # The "BatchTableEnvImpl" creates the job pipeline with an empty cached file
> list, the cached files registered in the "BatchTableEnvImpl.execEnv" are
> dropped.
> # The "StreamPlanner" wraps the real "StreamExecutionEnvironment" into a
> "DummyStreamExecutionEnvironment", and the getConfiguration() method in the
> "DummyStreamExecutionEnvironment" is not delegated to the real
> "StreamExecutionEnvironment". It always returns an empty configuration object.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
