[
https://issues.apache.org/jira/browse/YARN-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14384609#comment-14384609
]
Li Lu commented on YARN-3047:
-----------------------------
Given the current discussion in YARN-3051, seems for now we have not reached a
rough conclusion on the V2 timeline reader APIs. In the patch of this JIRA,
we're simply assuming the very least subset of reader APIs, but in the
foreseeable future we may probably add more to support more v2 queries. We may
want to minimize such kind of iterations. IMHO, the reader layer should depend
on the reader APIs, but not the other way around. That said, we may want to
pause this JIRA until we have a relatively workable v2 API. After we feel we're
fine with the APIs, we can then rebase the patch to connect the relatively
simple wire up works here.
> [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)
