[
https://issues.apache.org/jira/browse/FLINK-20212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17237431#comment-17237431
]
Aljoscha Krettek commented on FLINK-20212:
------------------------------------------
Yes, I'm afraid we cannot change this. Our commandline parser has always been
"lenient": starting with the first unrecognized option we pass everything
through as is.
This is where we're calling into the external parser:
https://github.com/apache/flink/blob/c1a12e925b6ef46ad5cf0e0a5723949572550e9b/flink-clients/src/main/java/org/apache/flink/client/cli/CliFrontendParser.java#L487.
We could change this if we did a clear separation between framework arguments
and user arguments, à la {{bin/flink run --sys-arg1 foo --sys-arg2 bar
MyProgram.jar -- --user-arg1 boogle}}.
I would suggest closing this issue because it's currently working as designed.
Mind you, I'm not saying that the design is good here, because I don't think it
is!
> Fail command line interfaces when provided with an unrecognized option
> -----------------------------------------------------------------------
>
> Key: FLINK-20212
> URL: https://issues.apache.org/jira/browse/FLINK-20212
> Project: Flink
> Issue Type: Bug
> Components: Command Line Client, Deployment / YARN
> Affects Versions: 1.12.0
> Reporter: Robert Metzger
> Priority: Major
> Labels: usability
>
> Based on the discussion in FLINK-19461, we can improve the usability of Flink
> by failing if a user provided an unrecognized option.
> This will help users debug typos, or misunderstandings reading the
> documentation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
