Li Lu commented on YARN-3051:

bq. Want to loop in Li Lu and Vrushali C. Guys, would it be a non-trivial 
requirement to enforce uniqueness of (cluster id, entity type, entity id) when 
it comes to storage?
My hunch is it should not be hard for both hbase and Phoenix if we have the 
index table proposed by [~zjshen]:
bq. In addition, I think we need to have a index table such as <entity type, 
entity id, pointer to the entity in entity table> to support the single entity 
In phoenix, PKs cannot be identical. In hbase, we can check if the row key 
exists before we write to that cell. So I assume this is not hard. Am I missing 
anything here?

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