[ 
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-009.patch

sorry, missed that last update

this patch fixes the table formatting and adds the {{originalUrl}} field that 
is in the JSON examples but not in the table. Interesting, in slider our 
[SerializedApplicationReport|https://github.com/apache/incubator-slider/blob/b70d830aee6fc0171cb36fff0604b310dc565e3e/slider-core/src/main/java/org/apache/slider/core/launch/SerializedApplicationReport.java]
 data type is almost identical; If I'd known of this one I'd have skipped 
re-implementing it.

not fixing whitespace as per the comment in the review, {{--whitespace=fix}} 
does that when the patch is actually merged in. Instead I'll see if we can get 
that part of the patch review downgraded from a -1 to a warning.

> 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
>              Labels: BB2015-05-TBR
>         Attachments: HADOOP-11826-001.patch, HADOOP-11826-002.patch, 
> TimelineServer.html, YARN-3539-003.patch, YARN-3539-004.patch, 
> YARN-3539-005.patch, YARN-3539-006.patch, YARN-3539-007.patch, 
> YARN-3539-008.patch, YARN-3539-009.patch, timeline_get_api_examples.txt
>
>
> The ATS v2 discussion and YARN-2423 have raised the question: "how stable are 
> the ATSv1 APIs"?
> 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
(v6.3.4#6332)

Reply via email to