hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Li Lu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6069) CORS support in timeline v2
Date Tue, 21 Feb 2017 21:33:44 GMT

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

Li Lu commented on YARN-6069:

Sorry to chime in this late, but one general question about CORS itself. I'm not an expert
in this area so my concern may sound silly. In ATS v1, the only server will serve as both
reader and writer server, so my feeling is the CORS setting will affect both sides? In ATS
v2, we're only applying this setting to the reader server, but not on collectors. Is this
generally fine? Are writer APIs irrelevant in this case? Or, is this difference significant
enough that we need to separate configs or specially note this? Thanks! 

> 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

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

View raw message