[
https://issues.apache.org/jira/browse/FLINK-14250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16940609#comment-16940609
]
sunjincheng commented on FLINK-14250:
-------------------------------------
I'm glad to see this proposal [~aljoscha]！(y)
I think simplify the command-line parsing is a good idea. I go through the code
and share my thoughts as following:
How about we add a new `RunPyOption` and putting all the Python command-line
parsing logic into it. We can add the language check in `CliFrontend#run()` and
using `RunPyOption` if it's Python program. In this way, we can flexible extend
in future if we want to add other language support such as GO.
What do you think?
> 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)
