[
https://issues.apache.org/jira/browse/YARN-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14710102#comment-14710102
]
Li Lu commented on YARN-4074:
-----------------------------
I'd incline to use the latter approach to retrieve flows and flow runs, since
we don't actually differentiate them on the backend. I also incline to keep the
RESTful API layer simple, and to wrap it with a js native library for web UIs.
In this way we can separate the process of TimelineEntity retrieval and the
context of the timeline entities (e.g. is it a flow, or a application, or a DAG
of applications?). It's also much easier to maintain this interface IMO.
> [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
(v6.3.4#6332)
