[
https://issues.apache.org/jira/browse/YARN-2928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14308413#comment-14308413
]
Hitesh Shah commented on YARN-2928:
-----------------------------------
More questions:
What are the main differences between meta-data and configuration?
What search/sort/aggregate/count functionality is plan to be supported? It
seems based on the design doc, certain functionality is not supported on
configuration. Does this mean that it is simpler to dump all the data into the
meta-data to make it searchable?
Where does the current implementation's "otherInfo" and "primaryFilters" fit
in?
What use are events? Will there be a "streaming" API available to listen to all
events based on some search criteria? If there is a hierarchy of objects, will
there be support to listen to or retrieve all events for a given tree by
providing a root node?
How does an application define a relationship for its entity to a system entity?
> Application Timeline Server (ATS) next gen: phase 1
> ---------------------------------------------------
>
> Key: YARN-2928
> URL: https://issues.apache.org/jira/browse/YARN-2928
> Project: Hadoop YARN
> Issue Type: New Feature
> Components: timelineserver
> Reporter: Sangjin Lee
> Assignee: Vinod Kumar Vavilapalli
> Priority: Critical
> Attachments: ATSv2.rev1.pdf, ATSv2.rev2.pdf, Data model proposal
> v1.pdf
>
>
> We have the application timeline server implemented in yarn per YARN-1530 and
> YARN-321. Although it is a great feature, we have recognized several critical
> issues and features that need to be addressed.
> This JIRA proposes the design and implementation changes to address those.
> This is phase 1 of this effort.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
