Sangjin Lee commented on YARN-4074:

The queries we will need to support are as follows (let me know if you believe 
it's not accurate):

- given cluster, query the most recent N flows (from the flow activity table)
- (optionally) given cluster, user, flow id, query all flow runs

In terms of the implementation, there are two approaches. We can either define 
specific methods for querying for flow and flow runs, and implement them, or 
reuse the {{getEntities()}} method to implement them.

With the former approach, we might be having a proliferation of methods that 
are specific to types. On the other hand with the latter, the API may remain 
clean but the implementation would become messier with more if-else type of 

Personally I'm slightly leaning towards the latter, but I'd love others' 

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