You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Andrii Tkach (JIRA)" <ji...@apache.org> on 2014/06/10 18:01:03 UTC
[jira] [Commented] (AMBARI-6068) Ambari web client should use
stacks API instead of stacks2 API
[ https://issues.apache.org/jira/browse/AMBARI-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14026615#comment-14026615 ]
Andrii Tkach commented on AMBARI-6068:
--------------------------------------
https://reviews.apache.org/r/22418/
> Ambari web client should use stacks API instead of stacks2 API
> --------------------------------------------------------------
>
> Key: AMBARI-6068
> URL: https://issues.apache.org/jira/browse/AMBARI-6068
> Project: Ambari
> Issue Type: Task
> Components: client
> Affects Versions: 1.6.0
> Reporter: Andrii Tkach
> Assignee: Andrii Tkach
> Fix For: 1.6.1
>
>
> There are two hadoop stack endpoint
> {{http://localhost:8080/api/v1/stacks}}
> and
> {{http://localhost:8080/api/v1/stacks2}}
> Amabri web client uses stacks2 endpoint. Much of the work done in Ambari-1.6.0 for blueprint support is committed for stacks endpoint and it's not supported by stacks2 API.
> Stacks2 API is deprecated
> Ambari web client should also use stacks endpoint for consistency
--
This message was sent by Atlassian JIRA
(v6.2#6252)