flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chesnay Schepler (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FLINK-11853) Support POST for /jars/:jarid/plan
Date Wed, 27 Mar 2019 12:59:00 GMT

     [ https://issues.apache.org/jira/browse/FLINK-11853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Chesnay Schepler updated FLINK-11853:
    Summary: Support POST for /jars/:jarid/plan  (was: Allow  /jars/:jarid/plan as a POST
request too)

> Support POST for /jars/:jarid/plan
> ----------------------------------
>                 Key: FLINK-11853
>                 URL: https://issues.apache.org/jira/browse/FLINK-11853
>             Project: Flink
>          Issue Type: New Feature
>          Components: Runtime / REST
>            Reporter: Stephen Connolly
>            Assignee: Stephen Connolly
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 1.9.0
>         Attachments: flink-11853.patch
>          Time Spent: 20m
>  Remaining Estimate: 0h
> Lots of HTTP clients (including the Java native client as well as OkHttp) enforce that
a GET request cannot include a request body and change the request to a POST request if an
attempt is made to send a request body.
> While one answer would be to just request that people use a different HTTP client library,
in some cases the potential for classloader conflicts may make this difficult. The easier
solution would be to just provide a second end-point that responds to POST requests as well.

This message was sent by Atlassian JIRA

View raw message