[
https://issues.apache.org/jira/browse/YARN-6069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876503#comment-15876503
]
Varun Saxena commented on YARN-6069:
------------------------------------
Thanks [~rohithsharma] for the patch.
The configuration yarn.timeline-service.http-cross-origin.enabled is used for
both ATSv1.x and ATSv2 but the behavior is slightly different which is not
captured in yarn-default.xml. For instance, in ATSv1.x, if this configuration
is enabled, CrossOriginFilterInitializer will be added automatically but this
is not the case with ATSv2. How about the description below?
{code}
<description>Flag to enable cross-origin (CORS) support for timeline service
v1.x or Timeline Reader in
timeline service v2. For timeline service v2, also add
org.apache.hadoop.security.HttpCrossOriginFilterInitializer
to the configuration hadoop.http.filter.initializers in
core-site.xml.</description>
{code}
> 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, YARN-6069-YARN-5355.0003.patch,
> YARN-6069-YARN-5355.0004.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
