Details
-
Sub-task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
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.