You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Maximilian Michels (JIRA)" <ji...@apache.org> on 2016/06/25 15:40:37 UTC
[jira] [Resolved] (FLINK-3838) CLI parameter parser is munging
application params
[ https://issues.apache.org/jira/browse/FLINK-3838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maximilian Michels resolved FLINK-3838.
---------------------------------------
Resolution: Fixed
master: dfecca7794f56eb2a4438e3bdca6878379929cfa
release-1.0: f5a40855fbd90a375cb920358baaf176876a42f0
> CLI parameter parser is munging application params
> --------------------------------------------------
>
> Key: FLINK-3838
> URL: https://issues.apache.org/jira/browse/FLINK-3838
> Project: Flink
> Issue Type: Bug
> Components: Client
> Affects Versions: 1.0.2, 1.0.3
> Reporter: Ken Krugler
> Assignee: Maximilian Michels
> Priority: Minor
> Fix For: 1.1.0, 1.0.4
>
>
> If parameters for an application use a single '-' (e.g. -maxtasks) then the CLI argument parser will munge these, and the app gets passed either just the parameter name (e.g. 'maxtask') if the start of the parameter doesn't match a Flink parameter, or you get two values, with the first value being the part that matched (e.g. '-m') and the second value being the rest (e.g. 'axtasks').
> The parser should ignore everything after the jar path parameter.
> Note that using --<parameter name> does seem to work.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)