hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Varun Saxena (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4224) Change the ATSv2 reader side REST interface to conform to current REST APIs' in YARN
Date Mon, 14 Dec 2015 15:46:46 GMT

    [ https://issues.apache.org/jira/browse/YARN-4224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15056143#comment-15056143

Varun Saxena commented on YARN-4224:

IIUC, for PUT is the proposal to get UID first and then query again with this UID ?
So we will have have a uid endpoint and then form the UID(as a delimited string) at server
In what cases would we need a PUT from UI ?
Anyways from the GET side which is our immediate use case, if I understand, we will get a
set of flows and send UID in the same response for later queries ?
So I will have endpoints like {{flowrun/flowrun_UID}}, {{entities/entities_UID}},etc.
If we have all the info, cluster, user, flow, etc. can't we create a URL of the form {{/cluster_id/fuser/flow_name}}
? Are there any issues in Ember in creating such a URL ? Trying to understand why a flat URL
structure is necessary for Ember.
If I am not wrong we create the REST URL in JSONAPIAdapter in ember related code. Although
I faced some issues in linking two pages when I worked on it(not sure if this had to do something
with this), but anyways queries were being invoked with a hierarchical URL format(atleast
2 levels). 

Even if  UID is required what should be the delimiter ? What if flow name has the same delimiter
for instance. We need to handle it then.

If we need this format for UI, should we have this REST endpoint in addition to our current
REST endpoints(based on proposals above) for normal flow from clients ?

> Change the ATSv2 reader side REST interface to conform to current REST APIs' in YARN
> ------------------------------------------------------------------------------------
>                 Key: YARN-4224
>                 URL: https://issues.apache.org/jira/browse/YARN-4224
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>    Affects Versions: YARN-2928
>            Reporter: Varun Saxena
>            Assignee: Varun Saxena
>         Attachments: YARN-4224-YARN-2928.01.patch

This message was sent by Atlassian JIRA

View raw message