[
https://issues.apache.org/jira/browse/YARN-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Advertising
Varun Vasudev updated YARN-4009:
--------------------------------
Attachment: YARN-4009.001.patch
Uploaded the initial patch. It refactors the timeline service CORS support and
moves it into hadoop-yarn-server-common.
To preserve the current timeline service behaviour, I've renamed the classes to
YarnCrossOriginFilterInitializer and YarnCrossOriginFilter. The timeline
service CrossOriginFilterInitializer inherits from
YarnCrossOriginFilterInitializer and allows the existing configs to work
without any change.
I added a getPrefix function and modified the getFilterParameters function in
YarnCrossOriginFilterInitializer to allow it to be shared by the timeline
service and YARN.
[~jeagles], [~pramachandran] - can you please review the changes?
> 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
>
>
> 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)
