Li Lu commented on YARN-4224:

[~vrushalic] I think the proposal is pretty close to the hRaven form, just 
trying to combine the {{\{clustername\}/\{username\}}} part together with the 
flow's name to form an UID, so that some front end frameworks can easily access 
it. A problem here is the logic to build this UID would be better to be kept on 
the server side, that why we're proposing an "uid" end point for front end 
programs to build this UID when they would like to do a put (since they need to 
figure out the endpoint for this flow). 

[~Naganarasimha] I would not be surprised if most of the implementations of the 
proposed API are already in our codebase. We can simply change the "wrapper" 
layer of our reader server's WS to make this change.  

> Change the ATSv2 reader side REST interface to conform to current REST APIs' 
> in YARN
> ------------------------------------------------------------------------------------
>                 Key: YARN-4224
>                 URL: https://issues.apache.org/jira/browse/YARN-4224
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>    Affects Versions: YARN-2928
>            Reporter: Varun Saxena
>            Assignee: Varun Saxena
>         Attachments: YARN-4224-YARN-2928.01.patch

This message was sent by Atlassian JIRA

Reply via email to