Yep that was it. I have created
https://issues.apache.org/jira/browse/FLINK-11853 so that it is easier for
others to work around if they have restrictions on the HTTP client library
choice
On Thu, 7 Mar 2019 at 11:47, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
>
>
> On Thu, 7 Mar
On Thu, 7 Mar 2019 at 11:33, Chesnay Schepler wrote:
> I've heard of cases where client libraries are automatically changing
> the HTTP method when provided with a body.
>
Hmmm thanks for that... I'll dig into it
>
> To figure out what exactly is received by Flink, enable TRACE logging,
> try
I've heard of cases where client libraries are automatically changing
the HTTP method when provided with a body.
To figure out what exactly is received by Flink, enable TRACE logging,
try again and look for logging messages from
"org.apache.flink.runtime.rest.handler.router.RouterHandler"
On
In the documentation for the /jars/:jarid/plan endpoint
https://ci.apache.org/projects/flink/flink-docs-stable/monitoring/rest_api.html#jars-jarid-plan
It says:
> Program arguments can be passed both via the JSON request (recommended)
or query parameters.
Has anyone got sample code that sends th