Li Lu commented on YARN-4224:

bq. Anyways from the GET side which is our immediate use case, if I understand, 
we will get a set of flows and send UID in the same response for later queries ?
Yes, how about putting them as an "otherinfo" so that the front end can get 
this information? 

bq. If we have all the info, cluster, user, flow, etc. can't we create a URL of 
the form /cluster_id/fuser/flow_name ?
Having hierarchical IDs are possible in ember, but in general it's not a common 
practice. On this point, maybe [~leftnoteasy] has comments? 

bq. Even if UID is required what should be the delimiter ? What if flow name 
has the same delimiter for instance. We need to handle it then.
That's something we need to consider if we'd like to pursue this approach. We 
may need to restrict some special characters in our cluster id/user name/flow 

bq. If we need this format for UI, should we have this REST endpoint in 
addition to our current REST endpoints(based on proposals above) for normal 
flow from clients ?
I'd prefer to have them as the only style of endpoints for timeline v2. Right 
now we need to spend some work to rebuild REST endpoints in this style for AHS 
for the new UI. Right now in ATS v2 we're starting out fresh, therefore we 
don't need to handle the legacy use cases? 

bq. Moreover, what do you mean by batch query ? Does that mean support for 
multiple optional query parameters like filters etc. to trim down the results ? 
We already have them.
Yes. Let's make sure they have the same style as other endpoints (proposed in 
this JIRA) though. I don't think we need much work underneath the wrapper 

> 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