flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maximilian Michels (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-3838) CLI parameter parser is munging application params
Date Mon, 20 Jun 2016 12:27:05 GMT

    [ https://issues.apache.org/jira/browse/FLINK-3838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15339411#comment-15339411

Maximilian Michels commented on FLINK-3838:

A workaround is to use {{./flink run <flink options> <jar path> -- <jar arguments>}}
The two dashes tell the parsing library that no more options are following and it should take
the rest as it is.

> 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

View raw message