Jonathan Eagles commented on YARN-4009:

[~vvasudev], I'm trying hard to find a balance here. On the one hand I want to 
support backwards compatibility on the other hand I want configuration to be 
simple. I want to support way that I can enable only RM and timeline CORS 
support while only specifying the configuration once (not once for common CORS 
and once for timeline CORS). However, I want to support both the old 
configuration parameters.

1) If timeline CORS is enabled () we can have the timeline cors configuration 
override the common CORS if they are present otherwise use the common 
2) Create a second timeline enabled flag that will only use the new CORS 
classes, configs and behavior. This will allow the the old way using the old 
configs with timeline prefix to work, but allow users to migrate to the new way 
to simplify configuration.

What do you think?

> 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
> 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

Reply via email to