hadoop-yarn-issues mailing list archives

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

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

Vrushali C commented on YARN-3984:
----------------------------------

Great.. thanks.. 

bq. Secondly, how do we deal with an event without any info? How about creating a column "e!
eventid # inverse_event_timestamp ? dummy_key : empty_value"?

I am still thinking over this. But here is my line of thinking: I was going to create a "e!
eventid # inverse_event_timestamp?" column key with null value. So the column key will not
have any event key and event value. This way if the event key and value are both null, at
read time, the info map can also be null. 

> 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)

Mime
View raw message