hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Li Lu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3984) Rethink event column key issue
Date Fri, 31 Jul 2015 23:48:05 GMT

    [ https://issues.apache.org/jira/browse/YARN-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14650014#comment-14650014
] 

Li Lu commented on YARN-3984:
-----------------------------

Hi [~vrushalic], thanks for the patch. The current patch LGTM (pending Jenkins). Just to double
check that we need to firstly grab the event for the case its info map is empty, and then
if it fails we start to read all info keys? Thanks! 

> 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
>
>         Attachments: YARN-3984-YARN-2928.001.patch
>
>
> 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)

Mime
View raw message