[
https://issues.apache.org/jira/browse/YARN-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14615792#comment-14615792
]
Zhijie Shen commented on YARN-3051:
-----------------------------------
bq. The current FS implementation had cluster as part of the path. So there
will a app_flow_mapping.csv for each cluster. So in a way it is part of the
primary key even though its not there in app_flow_mapping.csv
I hope that is what your concern was.
The problem is about write path. Suppose we unfortunately have the duplicate
appId: one is clusterId1/appId and the other is clusterId2/appId. When the
former entity is written, you have added appId into the mapping file. How do
you write the mapping file upon cluster2/appId? Overwriting the row of appId?
Appending one more row of appId? Both will trouble you when finding the right
flow info when the query has default values.
> [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
> Affects Versions: YARN-2928
> Reporter: Sangjin Lee
> Assignee: Varun Saxena
> Attachments: YARN-3051-YARN-2928.003.patch,
> YARN-3051-YARN-2928.03.patch, YARN-3051-YARN-2928.04.patch,
> YARN-3051-YARN-2928.05.patch, YARN-3051-YARN-2928.06.patch,
> YARN-3051-YARN-2928.07.patch, YARN-3051-YARN-2928.08.patch,
> YARN-3051.Reader_API.patch, YARN-3051.Reader_API_1.patch,
> YARN-3051.Reader_API_2.patch, YARN-3051.Reader_API_3.patch,
> YARN-3051.Reader_API_4.patch, YARN-3051.wip.02.YARN-2928.patch,
> YARN-3051.wip.patch, 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)
