[
https://issues.apache.org/jira/browse/YARN-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14648491#comment-14648491
]
Vrushali C commented on YARN-3984:
----------------------------------
To reach a conclusion on this:
If everyone/most folks are +1 for putting the event timestamp before the event
id itself {code} e! inverse_event_timestamp # eventid ? eventkey {code} I can
go ahead and create the patch.
Note that by doing so, we will *always* have to query for all event ids and all
timestamps regardless of the query (unless we know the exact timestamp).
If not, the other option is to put the event timestamp after the event id but
before the event key.{code} e! eventid # inverse_event_timestamp ? eventkey
{code}
In this option, we have the option of querying for a particular event id.
In both cases, we need to fetch all records, construct TimelineEvent objects
and sort them for chronological order.
> 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)
