[
https://issues.apache.org/jira/browse/FLINK-14250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16939848#comment-16939848
]
Zili Chen edited comment on FLINK-14250 at 9/28/19 4:49 AM:
------------------------------------------------------------
Actually I am thinking of making {{CliFrontend}} the unique CLI frontend. This
is based on the fact that we have a dedicated {{FlinkYarnSessionCli}} and with
the abstraction of {{CustomCommandLine}} things grow a lot on complexity... If
only we can have a unique entrypoint like {{SparkSubmit}} in Spark.
FYI {{CustomCommandLine}} actually take some responsibility of configuration,
while some of ongoing effort try to make {{Configuration}} the unique interface
of configuration.
was (Author: tison):
Actually I am thinking of making {{CliFrontend}} the unique CLI frontend. This
is based on the fact that we have a dedicated {{FlinkYarnSessionCli}} and with
the abstraction of {{CustomCommandLine}} things grow a lot on complexity... If
only we can have a unique entrypoint like {{SparkSubmit}} in Spark.
> 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)
