hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Eagles (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2277) Add Cross-Origin support to the ATS REST API
Date Fri, 08 Aug 2014 21:09:11 GMT

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

Jonathan Eagles commented on YARN-2277:
---------------------------------------

[~zjshen], Thank you for you feedback as this is going to have a much bigger impact on Hadoop
as a whole. I have provided a minimal CORS filter that will give us an idea if this is the
direction to go. Based on the direction of this patch, the scope has widened to create a general
CrossOriginFilter for use within all Hadoop REST APIs. Probably, we will want to split the
different pieces us across JIRAs, umbrella, Filter and FilterInitializer, additional configuration,
and individual REST servers. This way we can focus on the end goal of getting Tez UI done
in a timely manner without forgetting completeness of CORS support.

> Add Cross-Origin support to the ATS REST API
> --------------------------------------------
>
>                 Key: YARN-2277
>                 URL: https://issues.apache.org/jira/browse/YARN-2277
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Jonathan Eagles
>            Assignee: Jonathan Eagles
>         Attachments: YARN-2277-CORS.patch, YARN-2277-JSONP.patch, YARN-2277-v2.patch,
YARN-2277-v3.patch, YARN-2277-v3.patch
>
>
> As the Application Timeline Server is not provided with built-in UI, it may make sense
to enable JSONP or CORS Rest API capabilities to allow for remote UI to access the data directly
via javascript without cross side server browser blocks coming into play.
> Example client may be like
> http://api.jquery.com/jQuery.getJSON/ 
> This can alleviate the need to create a local proxy cache.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message