Vinod Kumar Vavilapalli commented on YARN-3539:

bq. So I'm not sure if it's good timeline now, as we foresee in the near 
future, we're going to be upgraded to ATS v2, which may significantly refurnish 
the APIs.
How about we simply say that people can continue to run the v1 Timeline Service 
(Single server backed by LevelDB) beyond Timeline Service next-gen? That way, 
older installations and apps can continue to use the old APIs, and the new APIs 
do not need to take the unknown burden of making the old APIs work on the newer 

> 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
> 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

Reply via email to