[
https://issues.apache.org/jira/browse/YARN-6069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15869094#comment-15869094
]
Varun Saxena edited comment on YARN-6069 at 2/16/17 3:53 AM:
-------------------------------------------------------------
As of now for timeline service, we use the timeline specific configurations if
they are configured and fall back to common configurations in
HttpCrossOriginFilterInitializer, if not configured.
Now for ATSv2 we can potentially use common configurations itself. As ATSv2 is
new, we can probably define it this way.
However this does not give us flexibility of switching off CORS for some
modules and not for some(if same configuration is used). But I wonder why
someone would be doing it i.e. switch off CORS for some and not switch it off
for other.
was (Author: varun_saxena):
As of now for timeline service, we use the timeline specific configurations if
they are configured and fall back to common configurations in
HttpCrossOriginFilterInitializer, if not configured.
Now for ATSv2 we can potentially use common configurations itself. As ATSv2 is
new, we can probably define it this way.
> 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
>
>
> 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
