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 2019/09/27 13:07:00 UTC
[jira] [Commented] (FLINK-14250) Introduce separate "bin/flink
runpy" and remove python support from "bin/flink run"
[ https://issues.apache.org/jira/browse/FLINK-14250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16939427#comment-16939427 ]
Aljoscha Krettek commented on FLINK-14250:
------------------------------------------
This would be breaking for existing users that use "bin/flink run" for Python programs.
cc [~sunjincheng121], [~dianfu] (because of Python), [~Tison] (because of the ongoing executor work), what do you think about this?
> Introduce separate "bin/flink runpy" and remove python support from "bin/flink run"
> -----------------------------------------------------------------------------------
>
> Key: FLINK-14250
> URL: https://issues.apache.org/jira/browse/FLINK-14250
> Project: Flink
> Issue Type: Sub-task
> Components: Client / Job Submission
> Reporter: Aljoscha Krettek
> Priority: Major
>
> Currently, "bin/flink run" supports both Java and Python programs and there is quite some complexity in command line parsing and validation and the code is spread across different classes.
> I think if we had a separate "bin/flink runpy" then we could simplify the parsing quite a bit and the usage help of each command would only show those options that are relevant for the given use case.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)