hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-3539) Compatibility doc to state that ATS v1 is a stable REST API
Date Thu, 30 Apr 2015 17:19:06 GMT

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

Steve Loughran updated YARN-3539:
    Attachment: YARN-3539-005.patch

patch -005

h3. Valid entity types.

Currently "/" and " " are allowed in entity types. I'm not sure that is a good idea. I'd also
worry about "<" and ">" for security reasons. A regexp of A-Za-z0-9 + others of a limited
set may be enough. We can always check with all known users to see what entity types they
are using. Locking it down for V1 allows v2 to be consistent.

bq. 1. For the bullet points of "Current Status and Future Plans", can we organize them a
bit better. For example, we partition them into the groups of a) current status and b) future
plans. For bullet 4, not just history, but all timeline data.


bq. 2. Can we move "Timeline Server REST API" section before "Generic Data REST APIs"?


bq. 3. Application elements table seems to be wrongly formatted. I think that's why site compilation
is failed.


bq. 4. "Generic Data REST APIs" output examples need to be slightly updated. Some more fields
are added or changed.

Those are the examples from YARN-1876. If you have some more up to date ones I'll replace


bq. 5. "Timeline Server REST API" output examples are not genuine. Perhaps, we can run a simple
MR example job, and get the up-to-date timeline entity and application info to show as the

+1. Do you have this?

> Compatibility doc to state that ATS v1 is a stable REST API
> -----------------------------------------------------------
>                 Key: YARN-3539
>                 URL: https://issues.apache.org/jira/browse/YARN-3539
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: documentation
>    Affects Versions: 2.7.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>         Attachments: HADOOP-11826-001.patch, HADOOP-11826-002.patch, YARN-3539-003.patch,
YARN-3539-004.patch, YARN-3539-005.patch
> The ATS v2 discussion and YARN-2423 have raised the question: "how stable are the ATSv1
> The existing compatibility document actually states that the History Server is [a stable
REST API|http://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-common/Compatibility.html#REST_APIs],
which effectively means that ATSv1 has already been declared as a stable API.
> Clarify this by patching the compatibility document appropriately

This message was sent by Atlassian JIRA

View raw message