[
https://issues.apache.org/jira/browse/SPARK-3454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14308324#comment-14308324
]
Marcelo Vanzin commented on SPARK-3454:
---------------------------------------
Hi [~imranr],
There are two ways I can see to solve the routing problem:
The first is the one you mention. I like it because, as you say, it keeps the
API consistent across different UIs. You always look at "/json", not some
subpath that depends on which daemon you're looking at.
The second is to remove the notion of an "application list" from this spec.
That means the "/json" tree would be mounted under the application's path, not
at the root of the web server. The downside is that when you add an API to list
applications to the master / history server, things will look weird (you have
"/json/v1/applications" and "/{applicationId}/json/v1" instead of a single
tree). Clients would have to adapt depending on whether they're talking to an
app directly, or to the master / history server.
So yeah, I like your suggestion better.
> Expose JSON representation of data shown in WebUI
> -------------------------------------------------
>
> Key: SPARK-3454
> URL: https://issues.apache.org/jira/browse/SPARK-3454
> Project: Spark
> Issue Type: Improvement
> Components: Web UI
> Affects Versions: 1.1.0
> Reporter: Kousuke Saruta
> Attachments: sparkmonitoringjsondesign.pdf
>
>
> If WebUI support to JSON format extracting, it's helpful for user who want to
> analyse stage / task / executor information.
> Fortunately, WebUI has renderJson method so we can implement the method in
> each subclass.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
