[
https://issues.apache.org/jira/browse/YARN-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Eagles updated YARN-4009:
----------------------------------
Attachment: YARN-4009.8.patch
[~vvasudev], you are correct. There is no need for the new flag in the current
code base. Removed in patch 8. If
*yarn.timeline-service.http-cross-origin.enabled* is true then it will use
timeline conf values and the fall back to the common conf settings. I think
this is an acceptable compromise between backwards compatibility and utilizing
the new functionality.
> 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,
> YARN-4009.006.patch, YARN-4009.007.patch, YARN-4009.8.patch,
> YARN-4009.LOGGING.patch, YARN-4009.LOGGING.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)
