[
https://issues.apache.org/jira/browse/YARN-6069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15869957#comment-15869957
]
Varun Saxena edited comment on YARN-6069 at 2/16/17 1:54 PM:
-------------------------------------------------------------
Probably it did not come out clearly in my previous comment. I was alluding to
the same thing. That a user may look at timeline service related CORS
configurations and assume they are to be used for ATSv2 but till we document
clearly what the behavior is or configurations are, it should be fine. That is
why I said I am fine with either of the 2 approaches.
was (Author: varun_saxena):
Probably it did not come out clearly in my previous comment. I was alluding to
the same thing. That a user may look at timeline service related CORS
configurations and assume they are to be used for ATSv2 but till we document
clearly what the behavior is, it should be fine. That is why I said I am fine
with either of the 2 approaches.
> 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
