[
https://issues.apache.org/jira/browse/FLINK-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623860#comment-14623860
]
ASF GitHub Bot commented on FLINK-2218:
---------------------------------------
Github user mjsax commented on the pull request:
https://github.com/apache/flink/pull/904#issuecomment-120731470
Btw: CliFontend support the follows options: -c / --class , -m /
--jobmanager , -p / -- paralleslism
To have the same options, we might want to extend CliFontend for those.
What do you think? Furthermore, WebClient parses options -c and -p in an own
code path. This results in code duplication and manual synchronization of
options in CliFrontend and WebClient. We should reuse CliFrontend code in
WebClient (if possible). What do you think?
> Web client cannot distinguesh between Flink options and program arguments
> -------------------------------------------------------------------------
>
> Key: FLINK-2218
> URL: https://issues.apache.org/jira/browse/FLINK-2218
> Project: Flink
> Issue Type: Improvement
> Components: Webfrontend
> Affects Versions: master
> Reporter: Ufuk Celebi
> Assignee: Matthias J. Sax
>
> WebClient has only one input field for arguments. This field is used for
> Flink options (e.g., `-p`) and program arguments. Thus, supported Flink
> options restrict the possible program arguments. CliFrontend in contrast can
> distinguish both and thus `-p` can also be used as an program argument.
> Solution: add a second input field for Flink options to WebClient
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
