[
https://issues.apache.org/jira/browse/YARN-6069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15869054#comment-15869054
]
Rohith Sharma K S commented on YARN-6069:
-----------------------------------------
[~varun_saxena] I think you are missing one key thing is PREFIX is different
i.e *yarn.timeline-service.http-cross-origin* which is same as ATSv1. This is
the reason we have added new class. May be I can remove class
CrossOriginFilterInitializer and keep HttpCrossOriginFilterInitializer itself
for ATSv2 with the property *yarn.timeline-service.http-cross-origin.enabled*.
This will be much more simpler. I will update a different patch which uses
common code.
[~sunilg] Currently I have referred and borrowed it. It is done as same as
ATSv1. Lets change to different way inline with RM and NM.
> 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: [email protected]
For additional commands, e-mail: [email protected]
