Sangjin Lee commented on YARN-3049:

Then, we uniformly process the entities no matter what their type is. What we 
discussed so far implies that we cannot only treat the entities so generally. 
For application entity, we may need to take an additional step to parse its 
start/finish event to write more records.

I understand that we want to do that as much as possible. However, we made 
several calls in terms of schema that call out apps pretty explicitly, and to 
implement that some amount of special treatment of the application entities is 
required. For example, the app-to-flow table is already a special table for 
applications. Similarly, real-time aggregation takes values from application 
entities to the flow run level. I don't think it's as bad as it might sound.

> [Storage Implementation] Implement storage reader interface to fetch raw data 
> from HBase backend
> ------------------------------------------------------------------------------------------------
>                 Key: YARN-3049
>                 URL: https://issues.apache.org/jira/browse/YARN-3049
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Sangjin Lee
>            Assignee: Zhijie Shen
>         Attachments: YARN-3049-WIP.1.patch, YARN-3049-WIP.2.patch, 
> YARN-3049-WIP.3.patch, YARN-3049-YARN-2928.2.patch, 
> YARN-3049-YARN-2928.3.patch, YARN-3049-YARN-2928.4.patch, 
> YARN-3049-YARN-2928.5.patch
> Implement existing ATS queries with the new ATS reader design.

This message was sent by Atlassian JIRA

Reply via email to