[
https://issues.apache.org/jira/browse/YARN-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14652806#comment-14652806
]
Zhijie Shen commented on YARN-3049:
-----------------------------------
Okay, what will the timestamp be used to do? If there're too much context info
required, I agree it's not elegant to incrementally expose them to the backend.
One step back, I start to understand that the real situation actually deviates
from what I originally thought about the storage layer. When defining the data
model, I defined a generic TimelineEntity and make other first-class citizen
entities extend it. 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.
> [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
(v6.3.4#6332)
