[
https://issues.apache.org/jira/browse/YARN-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14649598#comment-14649598
]
Zhijie Shen commented on YARN-3984:
-----------------------------------
Sure, it's fine too. One question, do we make sure every event has such a
column or only the event without info has it? Personally, I prefer the former
option, which makes the process of the event uniformed.
> Rethink event column key issue
> ------------------------------
>
> Key: YARN-3984
> URL: https://issues.apache.org/jira/browse/YARN-3984
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Zhijie Shen
> Assignee: Vrushali C
> Fix For: YARN-2928
>
>
> Currently, the event column key is event_id?info_key?timestamp, which is not
> so friendly to fetching all the events of an entity and sorting them in a
> chronologic order. IMHO, timestamp?event_id?info_key may be a better key
> schema. I open this jira to continue the discussion about it which was
> commented on YARN-3908.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
