Using JAXRS isn't an issue here for me. The problem is that the JobManager fields [2] are initialized in the Servlet [1] via constructor; If I were to use a JAXRS endpoint I wouldn't be able to use those, unless the fields resided in a configuration file or could be passed around in some other way. Could you suggest some idea to solve this?
Also, is there a code style XML file I could import for using in Eclipse/IntelliJ? I had a look at the Contributing section of Flink and couldn't find one. [1]org/apache/flink/runtime/jobmanager/web/JobmanagerInfoServlet.java [2] /** Underlying JobManager */ private final ActorRef jobmanager; private final ActorRef archive; private final FiniteDuration timeout; On Tue, Jan 6, 2015, 2:24 PM Robert Metzger (JIRA) <j...@apache.org> wrote: > > [ https://issues.apache.org/jira/browse/FLINK-1228?page=com. > atlassian.jira.plugin.system.issuetabpanels:comment-tabpane > l&focusedCommentId=14265868#comment-14265868 ] > > Robert Metzger commented on FLINK-1228: > --------------------------------------- > > I think a subtask is not needed. This issue is clearly about adding a REST > interface to the JobManager. > > I don't know if any of the other Flink committers have ever worked with > JAXRS. You probably have to figure out how to use JAXRS yourself. > Feel free to change anything as needed (probably mostly inside the > "org.apache.flink.runtime.jobmanager.web" package). > > > 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) >
