Vrushali C commented on YARN-3984:

Thanks for filing the jira [~zjshen]. The key design will be based on the 
query/access pattern that we think is most relevant to this information. How do 
we envision this event information being accessed? Given an event id, do we see 
querying for most recent keys within an event as the primary access pattern? Or 
any time range based queries in fact. If yes, then putting the timestamp 
*before* the event key will be better. If the primary access pattern will be 
based on the name of the key in the event id, then putting the timestamp 
*after* the event key will make it work better. 

Do you have any example queries/access requests in mind? How was this 
information queried for in ATSv1? Who might be wanting this information? I 
think these questions will help us arrive at a solution. 

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

Reply via email to