[
https://issues.apache.org/jira/browse/YARN-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14495071#comment-14495071
]
Sangjin Lee commented on YARN-3051:
-----------------------------------
It is my view that the timeline service v.2 does not have to alter the
uniqueness of (entity type, entity id) except the addition of cluster id. One
could argue that even the addition of cluster id isn't really a change from v.1
as v.1 didn't envision multi-cluster storage, right?
My point is, addition of things like flows and users do not require changes in
the uniqueness semantics. Is there a strong reason to alter the uniqueness
semantics? As you point out, in theory the PK can allow different apps to have
the same (entity type + entity id), but it doesn't mean we HAVE to allow it. We
can clearly state that within the same cluster (entity type + entity id) must
be unique, and enforce it within the storage implementation. Thoughts?
> [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
(v6.3.4#6332)
