hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhijie Shen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-3814) REST API implementation for getting raw entities in TimelineReader
Date Thu, 30 Jul 2015 00:36:05 GMT

     [ https://issues.apache.org/jira/browse/YARN-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Zhijie Shen updated YARN-3814:
    Attachment: YARN-3814.reference.patch

I attached the patch which contains the web services only from the POC uber patch for your

The reason why I propose to have cluster ID in the path is to make it more like a *REST* API,
such that there's a hierarchical path from cluster to entityId. The reason why I only choose
clusterId, appId, entityType and entityId on the path is that we said these are the 4 pieces
can uniquely identify an entity in taxonomy (at least for now).

I'm not too worry about the default cluster ID problem. The user can read it from yarn configuration.
When we create the client lib to wrap over the REST API, we can load the default from there
if the user doesn't supply the clusterId.

> REST API implementation for getting raw entities in TimelineReader
> ------------------------------------------------------------------
>                 Key: YARN-3814
>                 URL: https://issues.apache.org/jira/browse/YARN-3814
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>    Affects Versions: YARN-2928
>            Reporter: Varun Saxena
>            Assignee: Varun Saxena
>         Attachments: YARN-3814-YARN-2928.01.patch, YARN-3814-YARN-2928.02.patch, YARN-3814.reference.patch

This message was sent by Atlassian JIRA

View raw message