[ https://issues.apache.org/jira/browse/YARN-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14648540#comment-14648540 ]
Sangjin Lee commented on YARN-3984: ----------------------------------- To be clear, with the latter option, if we want to look for an event by id, we can use {{ColumnPrefixFilter}} for {{e! eventId}}, right? So in that case we won't need to fetch all columns, correct? > 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)