[
https://issues.apache.org/jira/browse/YARN-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14942336#comment-14942336
]
Jonathan Eagles commented on YARN-4009:
---------------------------------------
+1. I have tried this patch out and reviewed the code. Minor nits
* Configuration usage set(_config setting_, 'true") is better as
setBoolean(_config setting_, true)
* timeline server now uses its own different way to enable. So if i turn on
resource manager and timeline server both on but nothing else, I get a CORS
disabled message in the timeline server log even though it is enabled. Could
you file a jira to address this spurious log message?
> CORS support for ResourceManager REST API
> -----------------------------------------
>
> Key: YARN-4009
> URL: https://issues.apache.org/jira/browse/YARN-4009
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Prakash Ramachandran
> Assignee: Varun Vasudev
> Attachments: YARN-4009.001.patch, YARN-4009.002.patch,
> YARN-4009.003.patch, YARN-4009.004.patch, YARN-4009.005.patch
>
>
> Currently the REST API's do not have CORS support. This means any UI (running
> in browser) cannot consume the REST API's. For ex Tez UI would like to use
> the REST API for getting application, application attempt information exposed
> by the API's.
> It would be very useful if CORS is enabled for the REST API's.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
