flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Ewen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-1228) Add REST Interface to JobManager
Date Wed, 24 Dec 2014 13:40:13 GMT

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

Stephan Ewen commented on FLINK-1228:

We currently have two web servers running:
 1) The JobManager server, which displays running jobs and cluster details.
 2) The WebClient, which only submits jobs and shows their execution plan. (This one is optional,
mus be started explicitly)

My first guess would be that this is a bit of a rework of the current design by unifying the
two servers into one and changing the design to follow the REST pattern.

Arvid described above a good way of mapping REST operations to our operations.

> 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
> 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

View raw message