Zhijie Shen commented on YARN-3051:

Hence, regardless the implementation detail, we logically use:

1. <entity type, entity id> to identify entities that are generated on the same 
2. <cluster id, entity type, entity id> to identify entities globally across 

In terms of compatibility, {{getTimelineEntity(entity type, entity id)}} can 
assume the cluster ID is either the default one or configured in yarn-site.xml.

Does it sound good?

> [Storage abstraction] Create backing storage read interface for ATS readers
> ---------------------------------------------------------------------------
>                 Key: YARN-3051
>                 URL: https://issues.apache.org/jira/browse/YARN-3051
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Sangjin Lee
>            Assignee: Varun Saxena
>         Attachments: YARN-3051_temp.patch
> Per design in YARN-2928, create backing storage read interface that can be 
> implemented by multiple backing storage implementations.

This message was sent by Atlassian JIRA

Reply via email to