[jira] [Comment Edited] (FLINK-1228) Add REST Interface to JobManager

["Ajay Bhat (JIRA)" <ji...@apache.org>]

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

Ajay Bhat edited comment on FLINK-1228 at 12/31/14 9:21 AM:
------------------------------------------------------------

Thanks [~StephanEwen].
Pls correct me if I'm wrong. The work to do would involve doing away with the  JobManagerInfoServlet  and creating a handler that's annotated with JAXRS "@GET" for the displaying of jobs.

Also, I notice that the writing of JSON is done manually for each job, which would prove difficult to maintain if the structure of job is changed. Is there a reason it is done this way and not done with standard json processors like Jackson?


was (Author: ajay bhat):
Thanks Stephen.
Pls correct me if I'm wrong. The work to do would involve doing away with the  JobManagerInfoServlet  and creating a handler that's annotated with JAXRS "@GET" for the displaying of jobs.

Also, I notice that the writing of JSON is done manually for each job, which would prove difficult to maintain if the structure of job is changed. Is there a reason it is done this way and not done with standard json processors like Jackson?

> Add REST Interface to JobManager
> --------------------------------
>
>                 Key: FLINK-1228
>                 URL: https://issues.apache.org/jira/browse/FLINK-1228
>             Project: Flink
>          Issue Type: Improvement
>            Reporter: Arvid Heise
>
> For rolling out jobs to an external cluster, we currently have 3 choices:
> a) Manual submission with Web Interface
> b) Automatic/Manual submission with CLClient
> c) Automatic submission with custom client
> I propose to add a way to submit jobs automatically through a HTTP Rest Interface. Among other benefits, this extension allows an automatic submission of jobs through a restrictive proxy.
> Rough idea:
> The web interface would offer a REST entry point for example /jobs. POSTing to this entry point allows the submission of a new job and returns the job URL. http://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-post-example.html
> GETting the job URL returns a small status.
> DELETING the job URL aborts the job.
> GETting on the /jobs returns a list of active and scheduled jobs.
> Since Flink already has a Jetty web server and uses Json for other services, the basic extension should require low effort. It would help Flink to be used inside larger corporations and align the interfaces with the other state-of-the-art MapReduce systems (s3, HDFS, HBase all have HTTP interface).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)