hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Akira AJISAKA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1999) Creating MapReduce REST API section
Date Fri, 02 May 2014 04:50:20 GMT

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

Akira AJISAKA commented on YARN-1999:
-------------------------------------

I'm also +1 (non-binding) for the change, and thanks [~ozawa] for taking this issue.
Here are three comments:
* HistoryServerRest.apt.vm looks deleted. You should {{git add}} the file and then create
a patch.
* Please remove the dead links from YARN REST APIs section in site.xml.
* When moving HistoryServerRest.apt.vm to MapReduce REST APIs section, it would be better
to change the sentence 
{code}
-  The history server REST API's allow the user to get status on finished applications. Currently
it only supports MapReduce and provides information on finished jobs.
{code}
like
{code}
The history server REST API's allow the user to get status on finished MapReduce jobs.
{code}
because the document itself is now MapReduce-specific.

> Creating MapReduce REST API section
> -----------------------------------
>
>                 Key: YARN-1999
>                 URL: https://issues.apache.org/jira/browse/YARN-1999
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 2.4.0
>            Reporter: Ravi Prakash
>            Assignee: Tsuyoshi OZAWA
>         Attachments: YARN-1999.1.patch
>
>
> Now that we have the YARN HistoryServer, perhaps we should move HistoryServerRest.apt.vm
and MapRedAppMasterRest.apt.vm into the MapReduce section where it really belongs?



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message