[
https://issues.apache.org/jira/browse/YARN-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14384998#comment-14384998
]
Sangjin Lee commented on YARN-3047:
-----------------------------------
I can understand both sides here. On the one hand, the scope of this JIRA
initially was to work out the basic structure of the timeline reader as a
daemon. On the other hand, the frontend APIs are intimately tied to the storage
reader API as well as the types of queries we need to support. Changes in one
are very likely to lead to changes in the other.
Either we commit this with the understanding that the frontend APIs are
basically a placeholder, or we combine this with the storage reader API work
(YARN-3051) and tackle it as a whole. Personally I'm fine with either approach,
whichever help us make progress...
> [Data Serving] Set up ATS reader with basic request serving structure and
> lifecycle
> -----------------------------------------------------------------------------------
>
> Key: YARN-3047
> URL: https://issues.apache.org/jira/browse/YARN-3047
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Sangjin Lee
> Assignee: Varun Saxena
> Attachments: Timeline_Reader(draft).pdf, YARN-3047.001.patch,
> YARN-3047.003.patch, YARN-3047.005.patch, YARN-3047.006.patch,
> YARN-3047.007.patch, YARN-3047.02.patch, YARN-3047.04.patch
>
>
> Per design in YARN-2938, set up the ATS reader as a service and implement the
> basic structure as a service. It includes lifecycle management, request
> serving, and so on.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
