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

Varun Saxena commented on YARN-6069:
------------------------------------

[~sunilg],
bq. I am behind such a linear approach and reuse existing capabilities. Its a 
matter having more configs.
Actually even in 1st patch we were using current configurations and not adding 
new ones. yarn timeline service CORS related configs exist already for ATSv1. 
And although 1st patch was not reusing code ATSv1 code, I suggested doing so by 
moving it to hadoop-yarn-server-common.

> CORS support in timeline v2
> ---------------------------
>
>                 Key: YARN-6069
>                 URL: https://issues.apache.org/jira/browse/YARN-6069
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelinereader
>            Reporter: Sreenath Somarajapuram
>            Assignee: Rohith Sharma K S
>         Attachments: YARN-6069-YARN-5355.0001.patch, 
> YARN-6069-YARN-5355.0002.patch
>
>
> By default the browser prevents accessing resources from multiple domains. In 
> most cases the UIs would be loaded form a domain different from that of  
> timeline server. Hence without CORS support, it would be difficult for the 
> UIs to load data from timeline v2.
> YARN-2277 must provide more info on the implementation.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to