[
https://issues.apache.org/jira/browse/FLINK-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14269146#comment-14269146
]
Robert Metzger commented on FLINK-1228:
---------------------------------------
Sorry, I don't fully understand the problem
Why can't you use fields like ActorRefs in JAXRS endpoints?
I guess its a pretty common use case that we have here? This sample code here
also seems to have fields:
http://www.hascode.com/2013/12/jax-rs-2-0-rest-client-features-by-example/.
> 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)
