[
https://issues.apache.org/jira/browse/FLINK-9832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16547670#comment-16547670
]
Ufuk Celebi commented on FLINK-9832:
------------------------------------
[~Zentol] I think this is a good approach for 1.6. For 1.5.2 I think it will
only benefit users that actually use the endpoint manually. I'm definitely OK
with closing this ticket and deprecating the query parameters in the long run.
Do you have an answer from the back of your head to the following question:
What happens if I use 1.5.0 and provide a POST body? Will those be just ignored
or will it result in an error?
> Allow commas in job submission query params
> -------------------------------------------
>
> Key: FLINK-9832
> URL: https://issues.apache.org/jira/browse/FLINK-9832
> Project: Flink
> Issue Type: Bug
> Components: REST
> Affects Versions: 1.5.1
> Reporter: Ufuk Celebi
> Assignee: Chesnay Schepler
> Priority: Blocker
> Fix For: 1.5.2, 1.6.0
>
>
> As reported on the user mailing list in the thread "Run programs w/ params
> including comma via REST api" [1], submitting a job with mainArgs that
> include a comma results in an exception.
> To reproduce submit a job with the following mainArgs:
> {code}
> --servers 10.100.98.9:9092,10.100.98.237:9092
> {code}
> The request fails with
> {code}
> Expected only one value [--servers 10.100.98.9:9092, 10.100.98.237:9092].
> {code}
> As a work around, users have to use a different delimiter such as {{;}}.
> The proper fix of this API would make these params part of the {{POST}}
> request instead of relying on query params (as noted in FLINK-9499). I think
> it's still valuable to fix this as part of a bug fix release for 1.5.
> [1]
> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Run-programs-w-params-including-comma-via-REST-api-td19662.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
