Vrushali C commented on YARN-4074:

My take is that we can make things as generic as possible but we should have 
separate apis for flows and flow runs. 

I had put up an initial proposal for flow based queries in ATS when we started 
off on this at 

I believe for the two queries you have listed above [~sjlee0], there would be 
two rest apis as:

1) Get All Flows
Path: /listFlows/<cluster>/
Returns: paginated list of apps with aggregated stats (to populate the flows 
list tab on the UI)
Sample URL:
This would be an UI related aggregation query

2) Get specific Flow's runs
Path: /flow/<cluster>/<user>/<flowName>/[version]
Returns: list of flows
Sample URL: 

> [timeline reader] implement support for querying for flows and flow runs
> ------------------------------------------------------------------------
>                 Key: YARN-4074
>                 URL: https://issues.apache.org/jira/browse/YARN-4074
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>    Affects Versions: YARN-2928
>            Reporter: Sangjin Lee
>            Assignee: Sangjin Lee
> Implement support for querying for flows and flow runs.
> We should be able to query for the most recent N flows, etc.
> This includes changes to the {{TimelineReader}} API if necessary, as well as 
> implementation of the API.

This message was sent by Atlassian JIRA

Reply via email to