[
https://issues.apache.org/jira/browse/YARN-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14497315#comment-14497315
]
Vrushali C commented on YARN-3051:
----------------------------------
Hi [~varun_saxena]
As per the discussion in the call today, here is the query document about flow
(and user and queue) based queries that I had mentioned (put up on jira
YARN-3050)
https://issues.apache.org/jira/secure/attachment/12695071/Flow%20based%20queries.docx
Also, some points that I think may be helpful:
- the reader API is not going to be limited to one or two api calls
- different queries will need different core read apis. For instance, all flow
based queries may not need the application id or entity id info, but rather
would need the flow id. for example, for a given user, return the flows that
were run during this time frame. This query requires only cluster and cluster
info, not entity nor application nor flowname is needed for the reader API to
serve this query. This query cannot be boiled down to an entity level query.
- So the reader API should allow for entity level, application level, flow
level, user level, queue level and cluster level queries.
> [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.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)
