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

Josh Rosen commented on SPARK-3644:
-----------------------------------

[~cnstar9988]: there is some documentation for the 1.4.0 REST API at 
http://spark.apache.org/docs/latest/monitoring.html#rest-api.  You can also see 
the test cases in the pull request to see some sample requests / responses.

[~rnowling], I think that https://issues.apache.org/jira/browse/SPARK-5388 is 
the JIRA for covering REST APIs for job submission.  I think that the original 
scope of this JIRA was for application monitoring; if we want to discuss APIs 
for job submission or job-server-like functionality, then I think we should 
file more focused JIRAs for those specific issues.

> REST API for Spark application info (jobs / stages / tasks / storage info)
> --------------------------------------------------------------------------
>
>                 Key: SPARK-3644
>                 URL: https://issues.apache.org/jira/browse/SPARK-3644
>             Project: Spark
>          Issue Type: New Feature
>          Components: Spark Core, Web UI
>            Reporter: Josh Rosen
>            Assignee: Imran Rashid
>             Fix For: 1.4.0
>
>
> This JIRA is a forum to draft a design proposal for a REST interface for 
> accessing information about Spark applications, such as job / stage / task / 
> storage status.
> There have been a number of proposals to serve JSON representations of the 
> information displayed in Spark's web UI.  Given that we might redesign the 
> pages of the web UI (and possibly re-implement the UI as a client of a REST 
> API), the API endpoints and their responses should be independent of what we 
> choose to display on particular web UI pages / layouts.
> Let's start a discussion of what a good REST API would look like from 
> first-principles.  We can discuss what urls / endpoints expose access to 
> data, how our JSON responses will be formatted, how fields will be named, how 
> the API will be documented and tested, etc.
> Some links for inspiration:
> https://developer.github.com/v3/
> http://developer.netflix.com/docs/REST_API_Reference
> https://helloreverb.com/developers/swagger



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to