Li Lu commented on YARN-4074:

bq. As a general question, since we're returning our timeline entities as jsons 
in our web service, we need to some sort "rebuild" those entities on the js 
client side, right? If this is the case, we need to provide some js object 
model to be consistent with our TimelineEntity object model? I'm not a 
front-end expert so I'd like to learn the typical practice on this problem.
bq. I'm not intimately familiar with that either. I hope someone who's familiar 
could comment?

I was told by the HDFS community that they are using Dust 
(github.com/linkedin/dustjs) templates to do this. They have code available in 
our codebase as well. I'm planning to look into this framework in our POC 

> [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
>         Attachments: YARN-4074-YARN-2928.POC.001.patch, 
> YARN-4074-YARN-2928.POC.002.patch
> 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